Clean up logic to test if job is configuring
bug 3366

Do not launch a batch step while the job is configuring. Previous
  logic checked for the PrologSlurmctld running, but not nodes
  booting. Checking the job's CONFIGURING state flag will validate
  both.
bug 3366

Add check to avoid step allocation logic from executing job
  configuration completion logic multiple times (check if job
  is configurating before clearing flag and resetting time limit).
bug 3366

slurmctld/agent race condition fix: Prevent job launch while PrologSlurmctld
    daemon is running or node boot in progress.
bug 3366

This is required to manage the configuration completion.
bug 3366

This will be required to lock the job structure
bug 3366

Remove the return value from the agent_retry() function. It is not
  used anywhere and needs to be removed to run as a pthread.
bug 3366

Reasonable NFS systems do not need a minute to propagate changes.

If a lower version client would try to communicate with a higher version
controller the dbd would return the controller's version and the client
would use that version to talk to the controller. When the controller
would respond, the client wouldn't know how to unpack the higher version
msg.

'assoc_limit_stop'.

condition later when looking at a steps env.

Bug 3394

Bug 3398

bug 3399

bug 3099

This reverts commit e92b49d3.

No functional change.

instead of also in the backfill scheduler.

Bug 3405.

acct_policy_job_runnable_pre_select() calls assoc_mgr_set_qos_tres_cnt()
without tres READ_LOCK.

Note that existing code does not modify the tres structures, so this
cannot currently lead to a race condition.

Bug 3406.

job_submit/cnode was previously removed by commit 63bc71ed.

Bug 3403.

Bug 3395

burst_buffer/cray - Avoid "pre_run" operation if not using buffer (i.e.
    just creating or deleting a persistent burst buffer).
bug 3391

Previous job state information was "PENDING" rather than "REQUEUED"
  for each job requeued due to a burst buffer error.
bug 3388

scheduling a Datawarp job.

The assoc_mgr lock needs to happen before the bb_state.bb_mutex.  One place
this could cause deadlock is from src/slurmctld/controller.c
_accounting_cluster_ready() which calls clusteracct_storage_g_cluster_tres
which inturn calls bb_g_job_set_tres_cnt which calls bb_p_job_set_tres_cnt
which will lock the bb_muxtex after the assoc_mgr is already locked.

Bug 3389

Cache results of bit_set_count() calls.

Bug 3393.

Accidentally commited to Slurm version 16.05 instead of master

3 places where a string pointer referenced an out-of-scope memory location
1 memory leak and
1 unterminated string

backfill scheduler: Stop trying to determine expected start time for a job
    after 2 seconds of wall time. This can happen if there are many running jobs
    and a pending job can not be started soon.
byg 3373

mobile devices didn't behave as expected.

some of the tables (prolog_epilog) were hard to read.

Bug 3364.

Bug 3376.