24.05.ug before reduce patches #69
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
22.05.ug merge
22.05.ug merge
fix: do not try to deref before pointer is initialised
Tag 22.05.6 release.
Tag 22.05.8 release.
Tag 22.05.9 release.
Update to 22.05.09
fix: also pass nnodes through the message
Ticket 21393 Cherry-picked: eca4a64
Address race condition where submitted jobs would occasionally start RUNNING when the test expected PENDING jobs. Tests running_vs_pending are now not necessary. Ticket 21393 Cherry-picked: d4ebd3f
Cherry-pick !228 into slurm-24.05 See merge request SchedMD/dev/slurm!230
If the backup controller is in control and scontrol reconfigure is run, after resuming the primary controller it was possible that the backup would not honor the request to relinquish control. In most cases this would result in the backup controller crashing, but in a quiet enough system both controllers could continue to operate as the primary. Changelog: slurmctld - Fix crash and possible split brain issue if the backup controller handles an scontrol reconfigure while in control before the primary resumes operation. Ticket: 21532 Cherry-picked: f37371b
Cherry-pick !218 into slurm-24.05 See merge request SchedMD/dev/slurm!238
The controller doesn't pack job_record_t's node_addrs, so the stepmgr wasn't getting them and passing them to the steps. When the steps completed and tried communicating back to the dynamic stepmgr, it failed to find its node addr. The job's node_addr's are passed in the cred so we can just get them from there. Changelog: Fix stepmgr not getting dynamic node addrs from the controller Ticket: 21535 Cherry-picked: a4af0fb
Changelog: stepmgr - avoid "Unexpected missing socket" errors. Ticket: 21422 Cherry-picked: 8469d65
Changelog: Fix `scontrol show steps` with dynamic stepmgr Ticket: 21422 Cherry-picked: 59e69f3
Cherry-pick !220 into slurm-24.05 See merge request SchedMD/dev/slurm!241
Cherry-pick !224 into slurm-24.05 See merge request SchedMD/dev/slurm!243
Cherry-picked: 5b80951
Cherry-pick !256 into slurm-24.05 See merge request SchedMD/dev/slurm!259
Cherry-picked: e47410a Ticket: 20997
Cherry-picked: 54e3c2b Ticket: 20997
Cherry-picked: 43a57d9 Ticket: 20997
Previous default behavior of trying IPv4 remains, however if the controller appears to be IPv6 only skip the IPv4 attempt. It is expected that all slurm controllers have the same IP address families available. Cherry-picked: bf4a853 Ticket: 20997
When using an IPv6 address directly, wrap the address with [] to denote what is address vs what is the port. Cherry-picked: 04babaa Ticket: 20997
Changelog: Support IPv6 in configless mode. Cherry-picked: 050517c Ticket: 20997
Cherry-pick !118 into slurm-24.05 See merge request SchedMD/dev/slurm!233
Update slurm.spec and debian/changelog as well.
itkovian
force-pushed
the
24.05.ug-before-reduce-patches
branch
from
f801b37 to
30a0b7d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the version we will update to first.