It wasn't doing it for origin jobs.

The persistent connection was being destroyed which closed the socket
which made it so that the response rc couldn't make it back to the
originating cluster.

e.g.
Jobs on cluster1 (fed:cluster)

since a multiple clusters could have the same node names.

Previously remote jobs would be removed from the job_list as quickly as
possible to prevent collisions with requeued jobs and to clear up the
jobs and the orign job would stay around till minjobage on the origin.
But the origin job didn't have the details from the job that ran on a
remote cluster.

Now just don't show revoked jobs. The origin tracking job will remain as
revoked and not shown and the remote job will hang around for display
till minjobage. scontrol show jobs will show the job from the cluster
that ran the job. The job is requeuable as long as the origin job is
still in the origin cluster's job_list.

Just check for the revoked state instead of checking if it's a tracker
job since an origin job will be revoked if it can't run on the origin or
if it's running on a remote cluster.

It's old code, but a newly report.

With commit 3e00ede5, _pack_job_alloc_info_msg wasn't hitting the
xassert as expected.

burst_buffer logic modified to support sizes in both SI and EIC size units
    (e.g. M/MiB for powers of 1024, MB for powers of 1000).
bug 3922

This patch removes a window in which a message bound for the DBD
could be packed with the non-dbd packing.  This would result in a
packed msg_type, but nothing else.  When that message was given to
the DBD it would complain forever about an unpacking error.

Bug 3891 and 3939

list functions.

# Conflicts:
#	src/slurmd/slurmd/req.c
#	src/srun/libsrun/allocate.c

done.

Pretty much remove 10cc6f93

Bug 3919

Makes testing with multiple-slurmd much nicer.

slurmctld would previously hide partitions from super-users by default.
That was changed in commit f6a20584
The test was modified to support that change in behaviour

workflows through the slurmd.

Bug 3833

CID 45140 and 45141

CID 171492

CID 171497

CID 171451

CID 171480

CID 171477

CID 717487

Unhandled return code makes Coverity sad, use the macro for
consistency in these cases and to silence the warnings.

Coverity noticed we don't consistently use it and started flagging these.
Switch to the macro for consistency.

The re-use of error_code results in the function returning an error
  when it really functions properly. Added new variable to use.

Use part_is_visible instead, which does not modify the partitions
(and thus require the part write lock).

No longer require part write lock.