Backfill scheduler: Test association and QOS node limits before reserving
    resources for pending job.
bug 2129

Prevents the following sequence from causing a segfault:
$ scontrol create partitionname=stuff nodes=ALL
$ sbatch --wrap="hostname" -o/dev/null -p stuff
Submitted batch job 1047468
$ scontrol delete partitionname=stuff
$ scontrol update jobid=1047468 partition=stuff

tree.

Bug 2006

step.

Previously only supported by SlurmUser and root.

Previously only reserved space for one task of pending job array.

Support taking node out of FUTURE state with "scontrol reconfig" command.
Previous logic would keep node in FUTURE state if that was the original
configuration when slurmctld started. If job was running on the node,
it will stay running, but the node make not be visible.

Make SLURM_ARRAY_TASK_MIN, SLURM_ARRAY_TASK_MAX, and SLURM_ARRAY_TASK_STEP
    environment variables available to PrologSlurmctld and EpilogSlurmctld.

We needed to send a finish from each node in the step whether it had
any activity or not.  This way the controller knew things were done
on the node and the data was sent to the database.

Bug 2097

Burst_buffer/cray: Don't stall scheduling of other jobs while a stage-in
    is in progress.
bug 2114

Fix to purge terminated jobs with burst buffer errors.
bug 2123

The prolog_running counter can now exceed 1. New logic raises limit
from 1 to 4 before preventing job recovery on restart.

Added burst_buffer.conf flag parameter of "TeardownFailure" which will
    teardown and remove a burst buffer after failed stage-in or stage-out.
    By default, the buffer will be preserved for analysis and manual teardown.
bug 2116

Bug 2106

What was happening was the calculation wasn't happening for memory
or nodes, just cpus and gres.

pre-increment.

The "dw_wlm_cli paths" command returns an error if no #DW options.

commit:508f866e

Bug 2095

Add logic to call the "setup" function.

in an hour counting multiple times.

Return permission denied if regular user tries to release job held by an
    administrator.
bug 2087

Fix creation of advanced reservation of cores on nodes which are DOWN.
There seems to be a bug with reservations using a node list (e.g.
Nodes=something + CoreCnt=something).  The result is a reservation made that's
arguably broken; listing the reservation (scontrol show reservation) will show
"Nodes=" (blank) and "CoreCnt=0".

It's very easy to reproduce, just by doing the following against a node in a
DOWN (also tested with POWER_UP) state:
scontrol create ReservationName=tmp_res StartTime=now EndTime=now+600
Nodes=<some_non_idle_node> CoreCnt=1 Users=<some_valid_user>
scontrol show reservation.
bug 2078