This commit fixes a bug we observed when combining select/linear with
gres. If an allocation was requested with a --gres argument an srun
execution within that allocation would stall indefinitely:

-bash-4.1$ salloc -N 1 --gres=gpfs:100
salloc: Granted job allocation 384049
bash-4.1$ srun -w j3c017 -n 1 hostname
srun: Job step creation temporarily disabled, retrying

The slurmctld log showed:

debug3: StepDesc: user_id=10034 job_id=384049 node_count=1-1 cpu_count=1
debug3:    cpu_freq=4294967294 num_tasks=1 relative=65534 task_dist=1 node_list=j3c017
debug3:    host=j3l02 port=33608 name=hostname network=(null) exclusive=0
debug3:    checkpoint-dir=/home/user checkpoint_int=0
debug3:    mem_per_node=62720 resv_port_cnt=65534 immediate=0 no_kill=0
debug3:    overcommit=0 time_limit=0 gres=(null) constraints=(null)
debug:  Configuration for job 384049 complete
_pick_step_nodes: some requested nodes j3c017 still have memory used by other steps
_slurm_rpc_job_step_create for job 384049: Requested nodes are busy

If srun --exclusive would have be used instead everything would work fine.
The reason is that in exclusive mode the code properly checks whether memory
is a reserved resource in the _pick_step_node() function.
This commit modifies the alternate code path to do the same.

(i.e ArchiveJobs PurgeJobs).  This is only a cosmetic change.

on slurmdbd startup.

lots of jobs.

BUG #1149

the SelectTypeParameters to magically set to CR_CPU.

did the ALPS reservation.  Bug 1115

The spank_fini() function is registered with atexit() to be called
after termination of the srun main() function. The registered
functions are inherited by the forked shepard process and thus
spank_fini() is called twice.
This commit fixes this problem by introducing a wrapper function
_call_spank_fini() that is a no-op in the context of the shepard
process.

Take more job options into consideration to estimate its node count.

the Slurm database.

At work in Sweden we often fika (coffee+buns and what have u) at 3PM. I sometimes accidentally give a start time of 'teatime', so when I return from 'fika' I see my job's just getting started. This fix should make life even easier for the Swedes.

Logs for jobs which are explicitly requeued will say so rather than saying
that a node in their allocation failed.

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).

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

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.

PrivateData=reservation modified to permit users to view the reservations
which they have access to (rather then preventing them from seeing ANY
reservation).

Add SchedulerParameters option of pack_serial_at_end to put serial jobs at
the end of the available nodes rather than using a best fit algorithm.

Also check for priority of zero in jobs submitted to multiple
partitions (priority zero means held, so set the priority to 1).

Disable include file specifications including hostname or IP address

Add ability to include other files in slurm.conf based upon the ClusterName,
hostname, and/or IP address.
bug 808