This patch has two parts:
1. When a job is intially submitted, the Slurm was failing to set
   an initial reason for the job not starting.
2. After a job was submitted, it was sometimes failing to reset
   the job's reason. It was also failing to reset the "last_job_update"
   time, so something like "squeue -i1" would not get the new reason.
bug 3025

Fix multipart srun submission with EnforcePartLimits=NO and job violating
    the partition limits.
bug 3025

bug 3011

If all GRES were not defined on all nodes OR if a regular expression was used
   for a GRES file configuration (e.g. in gres.conf
   "Type=gpu Files=/dev/nvidia[0-4]"), then memory corruption was likely.
   The logic has been bad since its inception several years ago.

POLLRDHUP does not exist on BSD, define to POLLHUP as done elsewhere.

The attached patch switches to a more reliable method of detecting
service nodes, using xtcli status. In addition, it switches to the print
function to be better compatible with python 3.

To ease the distribution process, plugin names will be automatically
adjusted to identify the version of API that it can support,
ie: pmix_v1 and pmix_v2.
This provides the ability for distro's to create separate
non-conflicting packages for each API generation.

Bug 2986

Insure reported expected job start time is not in the past for pending jobs.
bug 3002

burst_buffer/cray: Requeue, but do not hold a job which fails the pre_run
    operation.
bug 3009

Only mark job_id as zero for batch step (when all job steps would be
cleared), not for individual steps which prevented successive steps
from being cancelled.

Bug 2984.

slurmstepd modified to pre-load all relevant plugins at startup to avoid
    the possibility of modified plugins later resulting in inconsistent API
    or data structures and a failure of slurmstepd.
bug 2334

bug 2655

Bug 2983.

Don't about step launch if job reaches expected end time while node is
    configuring/booting (NOTE: The job end time will be adjusted after node
    becomes ready for use).
bug 2985

frequency other than AcctGatherNodeFreq.

Filesystem instead of Lustre.

Network dataset.

Locking slurmstepd in memory can result in exhausting real memory
  in some cases, resulting in failure of the slurmstepd process.
  This reverts commit 03cf4a5d,
  but the logic will be returned using a configuration parameter
  in Slurm version 17.02.
bug 2334

This should improve performance and prevent failure if a local
  group ID lookup fails.
bug 2928

Prevent slurmd abort if hwloc library fails to populate the "children"
    arrays (observed with hwloc version "dev-333-g85ea6e4").

Bug 2955.

Make EnforcePartLimit support logic work with any ordering of partitions
    in job submit request.
Developed jointly with Alejandro Sanchez <alex@schedmd.com>
bug 2920

Calculation switched the node count in place of the cpu count, which
results in incorrect estimates.

CID 44784.

CID 44787.

Bug 2950. Also identified as CID 56684 (copy+paste error).

CID 45023 and 45024.

Fix task:CPU binding logic for some processors. This bug was introduced
in version 16.05.1 to address KNL bunding problem.
bug 2972

Needed due to part_filter_set() calls; without write lock this can race
returning inconsistent results to 'sinfo'.

Bug 2958.

Regression test fixes if SelectTypePlugin not managing memory and no node
    memory size set (defaults to 1 MB per node).

Fix race condition in the account_gather plugin that could result in job
    stuck in COMPLETING state.
bug 2973

Prior logic used to create an advanced reservation based upon a core
  count would ignore the specialized cores. Then when a job tried to
  use the reservation, it would consider the specialized cores and
  not be able to use the core count used in the reservation creation.
  This change considers specialized cores when creating the reservation.

If slurmstepd had been swapped out before upgrade happened it could
  easily lead to SIGBUS at any time after upgrade. Prevent that by
  mlocking it.
bug 2334