Restore ability to manually power down nodes, broken in 15.08.12
in commit b4904661

The patch introduced in commit b4904661 (not powering down dead node) has a bad side effect.  Adding the "(node_ptr->last_idle != 0)" condition prevents from powering down nodes with the following command:

scontrol update nodename=nX state=power_down

because the state update function relies on zeroing the "last_idle" variable when a power_down is requested (see src/slurmctld/node_mgr.c, line 1589).

Reverting this commit should solve the problem...but I let you decide...

Didier GAZEN

node_features/knl_cray: If a node is rebooted outside of Slurm's direction,
    update it's active features with current MCDRAM and NUMA mode information.
bug 3071

Fix race condition that could result in MCDRAM state information coming
  from capmc rather than cnselect (used state for next boot rather than
  latest boot).
bug 3080

No functional change, just silencing the warning message in this instance.

Bug 3079.

Bug 3073.

Modify srun task completion handling to only build the task/node string for
    logging purposes if it is needed. Modified for performance purposes.
bug 3044

This reverts commit 1ec2a4ae.

Bug 3063.

Restructure srun command locking for task_exit processing logic for improved
  parallelism. This change decreases the amount of time consumed by serial
  logic by 2 orders of magnitude.
bug 3044

Preserve node "RESERVATION" state when one of multiple overlapping
    reservations ends. Previous logic would clear the node's
    RESERVATION state flag when any one of the reservations on the
    node ended rather than keeping the node in RESERVATION state
    until the last reservation ended.
bug 3057

Handle case when slurmctld daemon restart while compute node reboot in
    progress. Return node to service rather than setting DOWN.
bug 3042

Add salloc_wait_nodes option to the SchedulerParameters parameter in the
    slurm.conf file controlling when the salloc command returns in relation to
    when nodes are ready for use (i.e. booted).
bug 3043

bug 3055

bug 3054

reservations.

sched/backfill - Check that a user's QOS is allowed to use a partition
    before trying to schedule resources on that partition for the job.
bug 3039

bug 3035 and 3009

Otherwise blade_cnt is potentially greater than
bit_size(jobinfo->blade_map) which leads to an assertion failure.

Bug 3033.

with hwloc.

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