Setting qos in env_batch.xml no longer works

[jonbob]

I have been running on chrysalis with the "high" qos by modifying env_batch.xml with the last directive in the following snippet:

    <directives>
      <directive> --job-name={{ job_id }}</directive>
      <directive> --nodes={{ num_nodes }}</directive>
      <directive> --output={{ job_id }}.%j </directive>
      <directive> --exclusive </directive>
      <directive> --qos=high </directive>
    </directives>
    ````
That has worked until recently, but now it seems to be ignored. I can still change the qos of a run after it has been submitted using scontrol, so it's not that chrysalis no longer recognizes it.

[rljacob]

The resulting .case.run file should look like this:

#!/usr/bin/env python3
#SBATCH  --job-name=run.20240808.piCtl.ne120pg2_r025_RRSwISC6to18E3r5.chrysalis.test2
#SBATCH  --nodes=80
#SBATCH  --output=run.20240808.piCtl.ne120pg2_r025_RRSwISC6to18E3r5.chrysalis.test2.%j
#SBATCH  --exclusive
#SBATCH  --qos=high
#SBATCH  --switches=4

But the --qos line is missing. Last CIME version where this worked: 438850986

[jasonb5]

I'm looking into this now. Thanks!

[jasonb5]

Ok found the issue, working on a fix.
@jonbob Just want to confirm the previous working behavior.

./cime/scripts/create_newcase --compset S --res f19_g16 --case test
cd test
./case.setup
./case.build
# edit env_batch.xml to add directive
./case.submit

[jonbob]

Sorry @jasonb5 -- I missed your comment. Yes, that is the workflow that previously added the qos correctly