Make note about Ubuntu systems and the autocomplete script.
Correct documentation about how 'Elapsed' time fields are printed with
sacct.
Alphabetize debug_flags2str
Minor documentation update
PGSQL - Notes about Postgres functionality being removed in the next
version of Slurm.
MYSQL - fix issue when rolling up usage and events happened when a cluster
was down (slurmctld not running) during that time period.
Minor web page updates
select/cons_res - Avoid extraneous "oversubscribe" error messages

This problem was reported by Harvard University and could be
reproduced with a command line of "srun -N1 --tasks-per-node=2 -O id".
With other job types, the error message could be logged many times
for each job. This change logs the error once per job and only if
the job request does not include the -O/--overcommit option.
Merge branch 'slurm-2.5' into slurm-2.6
select/cons_res - Add test for zero node allocation

I don't see how this could happen, but it might explain something
reported by Harvard University. In any case, this could prevent
an infinite loop if the task distribution funciton is passed a
job allocation with zero nodes.
sched/wiki2 - Correct CPU load reported to Moab

I'm running Slurm 2.6.0 and MWM 7.2.4 in our test cluster at the moment.  I happened to notice that node load reporting wasn't consistent- periodically you'd see a "sane" load reported in Moab, but most of the time the reported load was zero despite an accurate CPULoad value reported by "scontrol show node".

Finally got to digging into this.  It appears that the only time load was being reported properly was in the Moab scheduling cycle directly after slurmctld did a node ping.  In subsequent scheduling cycles the load (again, as reported by Moab) was back to zero.

The node ping is significant as that is the only time the node is updated- since the wiki2 interface only reports records that change, and the load record isn't changed, it isn't reported in the queries after the node ping.

Judging from this behavior, I'm guessing that Moab does not store the load value- every time it queries resources in Slurm it sets the node's load back to zero.

I've altered src/plugins/sched/wiki2/get_nodes.c slightly- basically moved the section that reports CPULOAD above the check for updated info (update_time > last_node_update).

So I don't know if this is the appropriate way to fix it.  The wiki specification that Adaptive has published doesn't seem to indicate how this should function.  Either MWM should assume the last value reported is still accurate or Slurm needs to report it for every wiki GETNODES command.

Anyway, the patch is attached, it seems to be working for me, and I've rolled it into our debian build directory.  YMMV.

Michael
Add contributor to team web page
Change node update time when CPU load is updated
Update NEWS to reflect several recent code changes
Have qsub.pl pass along return code from sbatch/salloc
Update reservation web page for new v2.6 features

core reservations and reservation prolog/epilog
Update topology info to match current v2.6 capabilties
revert back to previous id numbers
Fix race condition from commit a96b5ae780ad64089ed10e68bc3ae6d0ab39fd9b

Basically the system size has to be set up before you call the
priority/multifactor plugin.  If a job is finishing while the slurmctld
is starting then it would fatal on the init if it wasn't set up.
Fix infinite loop for one byte config file

Problem reported by BYU. slurm.conf included a file one byte in
length. Logic created a buffer one byte long and used fgets()
to read the file. fgets() reads one byte less than the buffer
size to include a trailing '\0', so it fails to read the file.