And do not list each individual sensor reading but just the computed
sum of each one grouped by key.

Bug5274

This is in anticipation of an upcoming change to the cgroup hierarchy
on a future CLE release.

Bug 5145.

Bug 3792.

Bug 3792.

Add new page, add to Makefile.am and run autogen.sh.

Update additional documentation to point at this new page.

Bug 3792.

which were marked down due to ResumeTimeout.

If a cloud node was marked down due to not responding by ResumeTimeout,
the code inadvertently added the node back to the avail_node_bitmap --
after being cleared by set_node_down_ptr(). The scheduler would then
attempt to allocate the node again, which would cause a loop of hitting
ResumeTimeout and allocating the downed node again.

Bug 5264

Bug 5180.

Bug 5206.

I was seeing rare failures on the test due to timing issues.
This increased timeout seems to fix the issue for me.

NONE was not documented.

Bug 5161

Avoid left-over test input file

No functional change.

Bug 4999.

There were two code paths building an allocation response by calling
its own static _build_alloc_msg() function:

1. src/slurmctld/proc_req.c
2. src/slurmctld/srun_comm.c

These two functions diverged and both had members that were not filled
in but were filled in the other. This patch makes it so we change the
signature of the one in proc_req.c to make it extern and then in
srun_comm.c we call this newly common function.

Also added cpu_freq_[min|max|gov] members in the common one since these
were the only members missing in proc_req.c function (the one in
srun_comm.c had more members missing, like all the ntasks_per*, account,
qos or resv_name).

Bug 4999.

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

Only trust MUNGE signed values, unless the RPC was signed by
SlurmUser or root.

CVE-2018-10995.

Already vetted by slurmctld/slurmd, no need to re-check here.

Do not defer until later, and do not potentially miss out on proper
validation of the user_name field which can lead to improper authentication
handling.

CVE-2018-10995.

If the auth value (from MUNGE) does not match the requested value,
ensure it is listed as a valid extended gid for that user instead.

Bug 5038.

Value of 2113 is where it fits in with 17.11, so pin it here.

Caused by pthread_cancel cleanup by commit e5f03971  in 17.11.6.

Bug 5181.

The race condition was created in a7c8964e in 17.11.6 when removing
the (unsafe) pthread_cancel code handling thread termination.

Bug 5164