ESLURMD_GID_NOT_FOUND where slurm would be a little over zealous
in treating missing a GID or UID as a fatal error.

cnodes in them.

that isn't a full midplane.

restart.

The change in function call order of commit e60abe43
resulted in slurmd daemons on front-end systems not registering with the
proper node name.

Conflicts:
	src/common/slurm_protocol_util.c

block correctly.

Conflicts:
	src/plugins/select/bluegene/bg_read_config.c
	src/slurmctld/job_mgr.c

This reverts https://github.com/hautreux/slurm/commit/35075c10995f4e83d0104662f147cd7b413d25f4
My version of RPM doesn't seem to understand the "replace"
parameter for %config, so rpm builds bomb out with
    Invalid %config token: replace
    Invalid %config token: replace

I think the default for %config is to not replace config
files, so I'm not sure this commit is needed. Since the
release agents are not really config files, but need to
be tightly coupled to the release of task/cgroup and
proctrack/cgroup, I would say the release agents should
be moved under /usr/libexec/slurm

At the very least, this commit needs to be reverted before slurm-2.3.1
in order to allow rpms to be built.

Thanks,
Mark Grondona

Report correct job "Reason" if needed nodes are DOWN, DRAINED, or
NOT_RESPONDING, "Resources" rather than "PartitionNodeLimit".

This insures that the job association pointer is correct for the job
in case the QOS permits partition limits to be over-ridden.

plugins in the slurmd.

    value for jobs.