- 08 Sep, 2015 1 commit
-
-
David Bigagli authored
-
- 02 Sep, 2015 4 commits
-
-
Nicolas Joly authored
Do not use full path for true utility in testsuite. Its location differ across systems (/bin/true on Linux and /usr/bin/true on BSD).
-
David Bigagli authored
-
Morris Jette authored
Previous logic would set the avail_node_bitmap when a node was powered down, even if the initial state was DOWN or DRAINED. This made the node available for allocation to a job, which we don't want until the DOWN or DRAIN state is cleared. bug 1893
-
Morris Jette authored
This reverts commits 7660da9e 5c386455 and f6c5302b
-
- 01 Sep, 2015 6 commits
-
-
Brian Christiansen authored
Bug 1741
-
David Bigagli authored
-
Danny Auble authored
-
David Bigagli authored
-
David Bigagli authored
-
Danny Auble authored
-
- 28 Aug, 2015 4 commits
-
-
Morris Jette authored
This problem is reproducible by launching a job then killing the slurmstepd process. Under those conditions, requeue the job if possible (i.e. batch job with requeue option/configuration). This patch also improves the slurmctld logging when this happens. bug 1889
-
David Bigagli authored
-
David Bigagli authored
-
Morris Jette authored
This is a change in logic from commit 00099596 The original commit corrected the logic from CPU to core count, but used the cores_per_socket count rather than computing the total core count (cores_per_socket * sockets). bug 1830
-
- 27 Aug, 2015 3 commits
-
-
Morris Jette authored
Correct RebootProgram logic when executed outside of a maintenance reservation. Previous logic would mark the node up upon response to the reboot RPC (from slurmctld to slurmc) and when the node actually rebooted, flag that as an unexpected reboot. This new logic checks the node's up time to not mark the compute node as being usable until the reboot actually takes place. but 1866
-
Morris Jette authored
For testing purposes, add a slurmd flag so that it appears the compute node has rebooted whenever slurmd restarts.
-
Danny Auble authored
association manager.
-
- 26 Aug, 2015 3 commits
-
-
Morris Jette authored
Prevent job array task ID from being reported as NO_VAL if last task in the array gets requeued. The problem is that when that task starts, the task bitmap entry for it stays set, but the task counter gets decremented. If that job then gets requeued, under some conditions a failure to schedule it results in the array_task_id in the job record getting set to NO_VAL. Then when building the job info to report for squeue/scontrol, the string showing the pending task ID's is not rebuilt due to that counter being zero. All indications are that the job runs fine, only the information reported to squeue/scontrol is wrong. bug 1790
-
Danny Auble authored
-
Danny Auble authored
-
- 25 Aug, 2015 2 commits
-
-
Brian Christiansen authored
Bug 1873
-
Danny Auble authored
or binary.
-
- 21 Aug, 2015 8 commits
-
-
Brian Christiansen authored
Bug 1831
-
Brian Christiansen authored
Bug 1869
-
Morris Jette authored
-
Daniel Ahlin authored
This change adds the AuthInfo configuration parameter to the g_slurm_auth_get_uid() and g_slurm_auth_get_gid() functions. Then continuing on - src/common/slurm_auth.h shows that the following functions are intended to take the auth_info argument: extern void * g_slurm_auth_create( void *hosts, int timeout, char *auth_info ); extern int g_slurm_auth_verify( void *cred, void *hosts, int timeout, char *auth_info ); extern uid_t g_slurm_auth_get_uid( void *cred, char *auth_info ); extern gid_t g_slurm_auth_get_gid( void *cred, char *auth_info ); g_slurm_auth_create and g_slurm_auth_verify seems to be OK now - but g_slurm_auth_get_uid and g_slurm_auth_get_gid are not (most cases will work anyway since the munge auth plugin will only use auth_info if the cred has not yet been verified - and in many instances it has - still I would assume passing the information to be the safe thing to do). I've attached two blind patches that just replaces null with slurm_get_auth_info() for these two functions.
-
Morris Jette authored
This is an refinement of commit 47f96cae with improved logging and a similar fix to another place with similar logic bug 1880
-
David Bigagli authored
-
Morris Jette authored
Fix gang scheduling/preemption issue that could cancel job at startup. I have not been able to reproduce the reported problem, but this should prevent the reported problem. bug 1880
-
Morris Jette authored
-
- 20 Aug, 2015 1 commit
-
-
David Bigagli authored
This reverts commit 406cb529. Conflicts: NEWS This works ok up until 1048576M then it will make the divisor 1048576 and when it goes to divide it only does it once instead of 2 times returning 1G instead of 1T. We have decided to wait until 15.08 for a no convert option to be added.
-
- 17 Aug, 2015 2 commits
-
-
Morris Jette authored
If an advanced reservation contains no nodes (e.g. licenses or burst buffers only), then avoid logic used to replace failed or failing nodes which would reference a node bitmap that is NULL, which would result in an abort
-
Morris Jette authored
-
- 14 Aug, 2015 5 commits
-
-
Morris Jette authored
No change in logic, just document the behaviour
-
Danny Auble authored
-
Daniel Ahlin authored
We are using a non-default AuthInfo configuration and based on log-messages we see I believe this is not properly handled in certain parts of the code. Typical log message: Aug 12 17:06:15 t02n20 slurmd[27001]: error: Munge encode failed: Failed to access "/var/run/munge/munge.socket.2": No such file or directory Aug 12 17:06:15 t02n20 slurmd[27001]: error: Creating authentication credential: Socket communication error Aug 12 17:06:15 t02n20 slurmd[27001]: error: stepd_connect to 3165.0 failed: Protocol authentication error Aug 12 17:06:15 t02n20 slurmd[27001]: error: If munged is up, restart with --num-threads=10
-
Morris Jette authored
-
Morris Jette authored
Unfortunately the reservation's core_bitmap is a global bitmap and the nodes in the system may have changed in terms of their node count or nodes have been added or removed. Make best effort to rebuild the reservation's core_bitmap on the limited information currently available. The specific cores might change, but this logic at least leaves their count constant and uses the same nodes bug 1850
-
- 11 Aug, 2015 1 commit
-
-
Morris Jette authored
This propagates the logic from commit aa81c550 into another place where the job CONFIGURING flag is set.
-