Even if main scheduler doesn't allocate resources for hetjobs, the
queue list should be composed by all types of jobs. Otherwise, lower
priority regular jobs could be allocated resources by main scheduler
while higher priority hetjobs are waiting for a backfill cycle.

Bug 6593.

Bug 6679

Instruct the backfill scheduler to attempt to start a heterogeneous job
as soon as all of its components are determined able to do so.

Bug 5579.

This could probably be extended to give back sockets and cores and
such, but at this moment I really only needed how many threads to deal
with and total cpus.

There are at least two points where this can return a false positive
error message which can be confusing for users.

Continuation dc583bd1

Bug 6437

Bug 6658

Bug 6658

Bug 6633.

Bug 6529

Bug 6529

Bug 6529

Bug 6529

Update slurm.spec and slurm.spec-legacy as well.

Revert "Avoid errors from packing accounting_storage_mysql.so when RPM is built with out mysql support."

This reverts commit d18e26b9.

Backport of 21b9a39b

Bug 6625

Update slurm.spec and slurm.spec-legacy as well.

Print error: for each new line.

Bug 6142

Bug 6142

Bug 6584

response_cluster_rec stored a pointer to data in the controller config
that gets freed when the controller is reconfigured.

Bug 6584

Bug 6584

This should never happen, but is a nice safeguard.

Bug 6566

Bug 6612

All of the buffers are 24 characters, require the input string is
less than 23 characters and null combined to be parsed.

Remove regression added in b9699c2f

Bug 6636.

Contiuation of 9a243a1a

Bug 6592

Test was relying on seeing future jobs which is no longer the way it
works.

What was happening in a maintenance reservation was every 5 seconds
the slurmctld was sending a message to the slurmdbd telling it the
node's down/drain state was in a maintenance state as well.  We really
only needed to know about this once.

Bug 6487

(DRAIN+MAINT+IDLE) Before it would just print MAINT
Bug 6487

Bug 4296

This will be used in future commits.

Bug 4296

to avoid having to send alias list for cloud nodes that exist in DNS.
This is especially important for large cloud environments (e.g.
thousands of nodes) as the alias list environment will be too large for
execve().

Bug 6589

Bug 6587

This is useful in a cloud environment where the nodes come and go out of
DNS.

Bug 6592