Bug 5742

Bug 6398

On a heterogeneous system the gres.conf coming from various nodes
might not be complete.  The slurm.conf has a complete list of possible
gres on the other hand.

If the GRES doesn't exist we will print an error and use the id instead
of the name, but this should never happen.

Bug 6366

When trying to update the partition list of a job it didn't
get updated.

Bug 6329

pam_slurm_adopt so special users can ssh to a node. This is an
alternative to pam_access.so.

Bug 6243

Remove unneeded scontrol call.

Bug 6357

Bug 6357

Bug 6320

Bug 6004

specific tasks.

Bug 6357

Bug 6004

As noted by Josko Plazonic in the bug report, the tres_usage_in_max
value is bytes, whereas the script expects kb.

Bug 6004

Update seff to reflect API change from rss_max to tres_usage_in_max. Use
Slurmdb::find_tres_count_in_string to parse out the TRES_MEM value.

Bug 6004

Bug 5736

Bug 5736

Bug 5736

Bug 5736

Bug 5736

Bug 5736

Bug 6242

This check really is there to test if we have dynamic(inactive) features.

Obviously this doesn't work on heterogeneous systems, but there is no
good way to check for this as this check is used long before nodes are
considered.

Bug 6242

Docs updated with details. 'node' is simply removed from the tres list;
the report will continue if other valid tres are specified.

Bug 5954

Bug 6356.

Fixed srun from double printing invalid option
msg twice. Also removed the unused -b flag from sbatch.

Bug 6356.

Bug 5670.

Bug 5670.

Bug 5670.

SchedMD has moved to Utah, so change the jurisdiction.

The test21.30/inc21.30.11 does not work if SelectTypeParameters
does not manage memory (not a commonly used configuration), but
this adds a check to prevent a failure that is due to the
configuration rather than slurm code bug.

This patch fixes the regression caused by 07483564 where only the
linux plugin was handling this scenario correctly.

Bug 6332

Bug 5820.

Bug 6331

Added "Ben Roberts" to the team list

Bug #6336

Add a debug statement.

Bug 5823

When the backup slurmdbd is active, there is no need to print
connection errors every 10 minutes when the backup checks in on the
primary, at least at the 'error' level.

Prevent dbd clients, like sacctmgr, from printing a connection error
when running commands against the backup slurmdbd unless debug2.
Before, the clients would always print errors when trying to access
the primary dbd first.

Bug 5823

Fix issue introduced in commit 164d4878 that avoided a job to be modified
setting the current reservation to none.

Bug 6309

Bug 6217

TRESBillingWeights and PriorityWeightTRES.