Update NEWS, slurm.spec, and slurm.spec-legacy as well.

Previously with a configuration including FastSchedule=1 or 2,
GRES with files defined in gres.conf, and in the node configuration
either specified with a count of 0 or not included at all then
the node's GRES data would be built with a topology array containing
a GRES bitmap of zero size, resulting in an abort when trying to
operate on that bitmap.

bug 6997

Commit: 03165950

Bug 6466.

Bug 6466.

The name variable hasn't been set yet, so this is always NULL. Print the
uid/gid instead. While here, treat uid/gid as uint32_t, and use strtoul()
rather than atoi() to avoid issues with high-number uid/gid values.

Fixes GCC 9 warning.

Bug 7101.

Bug 7113

Coverity CID 198461

Bug 7112

Coverity CID 198464

Since the struct has an array, Clang complains about the use
of {0}. We decided to replace that with memset.

Bug 7096

Bug 6783

Co-authored-by: Alejandro Sanchez <alex@schedmd.com>

For testing purposes, disabling PrologFlags=Alloc seems reasonable.
If/when we actually need to support front-end systems in the future,
the underlying code will likely have changed and require additional
changes.

Bug 7057.

This reverts commit 123cb8e2.

The reason this code doesn't work is there are other flags set on the
job_state that make it not just Pending.

See test28.2.  It has the JOB_UPDATE_DB flag set.

Bug 7099.

commits:
e293204d
d5131780

Use RETRY_DELAY per to mirror job complete delay but without a max retry
count for the time being.

Bug 6970.

Bug 7040

Signed-off-by: Brian Christiansen <brian@schedmd.com>

Node state is 32bit. Have to wait till 20.02 to change packing routines.

See 845ff7d4

Bug 6964

Bug 6964

The reason was being set after the message was sent to the db. Also
clear the draing and reboot states before the message is sent so that
the event state will show DOWN.

Bug 6964

Bug 6964

so that new jobs can't get on the node.

Bug 6964

unnecessarily.

Bug 7106

Bug 6927

for completing job.

Bug 6927

If GRES are not bound to specific sockets in a multi-socket
node then the sock_gres->sock_cnt variable will be zero and
find no usable GRES on a node.

Bug 7095

specific sockets.

Bug 7019

This reverts commit 9cd7e5f4.

specific sockets.

Bug 7095

Continuations of 45bfc4dc

Bug 6926

Commits:
c2bc255c
f591f0c9

Bug 6926

The name variable hasn't been set yet, so this is always NULL. Print the
uid/gid instead. While here, treat uid/gid as uint32_t, and use strtoul()
rather than atoi() to avoid issues with high-number uid/gid values.

Fixes GCC 9 warning.

Bug 7101.

Continuation of 89b791bf.

Bug 7045.

To indicate that a job is dependent or has an invalid dependency.
Not used for now, just added and removed according to its meaning.

Bug 7045.

After 1d66b395 18.08 and 17.11 are the same so we can just reuse the
18.08 block instead of making a new one.

Bug 7080

Bug 7080

Bug 6467

Job steps that run on cloud nodes and use the alias_list - in other
words, SlurmctldParameters=cloud_dns is not in slurm.conf - all talk
directly back to the slurmctld. To make that happen, we set the parent
tank of each stepd to -1. However, we also set the rank of each stepd to
0. this meant that when each stepd sent a REQUEST_STEP_COMPLETE RPC to
the slurmctld, they would tell slurmctld to clean up node 0 in the step
allocation. So, multi-node step allocations weren't cleaning up after
the steps completed and would cause subsequent job steps to hang. The
step allocations would only clean up properly at the end of the job.

Ensure that each stepd uses the correct rank so that job steps are
properly cleaned up after each step completes.

Bug 6467.

They were associated to these two commits:

b4d7de48
6871185a

Bug 5562.

They were associated to these two commits:

b4d7de48
6871185a

Bug 5562.