This is a minor change to commit 4b8cdd4c
from yesterday and is needed to work with launch/poe (which was
broken by the commit).

a reservation.

which they have access to (rather then preventing them from seeing ANY
reservation).  Backport from 14.11 commit 77c2bd25.

arbitrary layouts (test1.59).

option (since it isn't).

Do not cause it to be rebooted (powered up).

This permits a sys admin to power down a node that should already
be powered down, but avoids setting the NO_RESPOND bit in the
node state. Doing so under some conditions prevented the node from
being scheduled. The downside is that the node could possibly be
allocated when it really isn't ready for use.

When a node's state is set to power_down, then execute SuspendProgram
even if previously executed for that node.

which protects against race conditions with the reservations.

Fix logic determining when job configuration (i.e. running node power up
logic) is complete. (Will look at better solution for v14.11).

When a node's state is set to power_up, then execute ResumeProgram even if
previously executed for that node.

different times when reservations are using the associations that are
being deleted.

A pointer was being used before a check for NULL value

a bitmap was not initialized, which could result in an assert

Requires priority/multifactor plugin with multiple partitions per job

Prior logic would always try to reserve nodes. This also slighly modifies
the reservation create logic for non-bluegene systems

Remove logic that was creating GRES bitmap for node when not needed (only
needed when GRES mapped to specific files).

Correct logic to support job GRES specification over 31 bits (problem
in logic converting int to uint32_t).