node_feature/knl_cray - Fix memory leak that can occur during normal
    operation. This will happen when an update request for a specific
    node happens.

If CnselectPath and/or SyscfgPath defined in knl_cray.conf file and
  slurmctld reconfigured, the original values of those paraemters
  would be over-written and their memory leaked.

Use FREE_NULL_BUFFER instead, otherwise we could attempt to
free_buffer a second time if we jump to the rwfail label.

bug4491

to preempt other eligible jobs.

Bug 4279

Missing from 390da8cf

Bug 4595

slurmdb_pack_assoc_usage() will assert with a NULL usage ptr.

7d9a75df uncovered that slurmdb_pack_assoc_usage() expects a usage
ptr.

Bug 4469

This is a continuation to c539d346 where this should had been removed
in the first place.

Bug 4127

bug 4539

When --mail-type option isn't requested with ARRAY_TASKS, we need somehow
to summarize the different states each task finished in the array. We've
added a new ARRAY_TASK_REQUEUED flag to the array_flags to indicate that
at least one task was requeued. Also the logic now detects if at least
one task failed and/or if otherwise all finished successfully.

The patch also removes the RunTime from the the e-mail when summarizing
whole array, since it doesn't make sense to specify just the RunTime
of one of the tasks for this case.

Patch also fixes when ARRAY_TASKS is specified, previously the mail
notification for the master job task record included a range of
ExitCodes for all the tasks. Since this option is not for summarizing,
the patch makes it so only the range is shown when the option isn't
specified.

Bug 4539.

Scheduling fix for changing node features without any NodeFeatures plugins.
Bug 4577

Bug 4329
Bug 4312

Avoid setting node in COMPLETING state indefinitely if the job initiating
the node reboot is cancelled while the reboot in in progress. Bug
introduced in commit 7d246784

Bug 4536

Bug 4448

Updated also some link references as agreed by e-mail with R. Castain.

Continuation of bbfd1890.

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

Logic was backwards before.

Bug 4459.

These tests were failing on a single node cluster

Refactor logging logic to avoid possible memory corruption on non-x86
    architectures.
bug 4469

There are out of memory conditions where spikes of memory usage hit the
limit set. When this happens (failcnt > 0), the Kernel might be able
to reclaim unused pages and the process can continue without oom-killer
actually killing the process. This may or may not result in an app
problem, thus we want to better clarify the message.

A separate bug will track the potential addition of a new feature to
better discern memory limits being hit from oom-killer actually killing
the process. There are mechanisms to register a notifier through the
cgroup.event_control control file, so that the application can be
notified through eventfd when OOM-Killer actually kills the process.

Bug 3820.

Link published to the slurm-users list by Ralph Castain:
https://pmix.github.io/pmix/how-to

only affects current 17.11 users tracking licenses or GRES in the database.

Bug 4553

# Conflicts:
#	src/plugins/accounting_storage/mysql/accounting_storage_mysql.c

increment ids for the tres_table.

Bug 4553

Turns out auto_increment=# doesn't work in MySQL at the time of writing
but does work correctly in MariaDB >=10.2.4+

See bug for more information.