[Bug Fix] Fix clustermgtd to detect bootstrap timeout so protected mode can trigger#702
Merged
hehe7318 merged 2 commits intoApr 30, 2026
Conversation
…de can trigger Compute nodes that hang during bootstrap (e.g. when a required VPC endpoint like DynamoDB is missing) loop indefinitely between ResumeTimeout and instance wake-up, because clustermgtd never counts them as bootstrap failures. Protected mode therefore never triggers and the cluster cannot stop the failing loop. Root cause: Slurm clears NOT_RESPOND on ResumeTimeout, producing state DOWN+CLOUD+POWERED_DOWN. The previous expected set included NOT_RESPONDING and never matched. Fix: drop NOT_RESPONDING from SLURM_SCONTROL_RESUME_FAILED_STATE so failing nodes are counted and protected mode triggers at the configured threshold.
gmarciani
approved these changes
Apr 30, 2026
This was referenced Apr 30, 2026
hehe7318
added a commit
to aws/aws-parallelcluster-cookbook
that referenced
this pull request
May 7, 2026
…ap (#3175) When a compute node cannot reach DynamoDB during bootstrap (for example, a private subnet is missing the DynamoDB VPC gateway endpoint), Chef's `ruby_block[retrieve compute node info]` retries silently with no useful diagnostic information. The default configuration (30 retries × ~5 min per attempt) also exceeds Slurm's default ResumeTimeout (2100s), so the instance is terminated before Chef can emit a final error. This change: - Tightens timeouts and retries so Chef fails fast within ResumeTimeout: - `retries`: 30 → 5 - `aws_connection_timeout_seconds`: 30 → 10 - `aws_read_timeout_seconds`: 60 → 30 - `shell_timeout_seconds`: 300 → 60 - Worst-case total time: ~5–6 minutes (under the 35 minutes `ResumeTimeout` default). - Improves the failure message to include the CLI exit code and stderr, plus a hint about the most common cause (missing DynamoDB VPC endpoint on a private subnet). - Fixes a pre-existing typo: `shell_timout_seconds` → `shell_timeout_seconds`. Related bug: aws/aws-parallelcluster-node#702
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of changes
Compute nodes that hang during bootstrap (e.g. when a required VPC endpoint like DynamoDB is missing) loop indefinitely between ResumeTimeout and instance wake-up, because clustermgtd never counts them as bootstrap failures. Protected mode therefore never triggers and the cluster cannot stop the failing loop.
Root cause: Slurm clears
NOT_RESPONDonResumeTimeout, producing stateDOWN+CLOUD+POWERED_DOWN. The previous expected set includedNOT_RESPONDINGand never matched.Fix: drop
NOT_RESPONDINGfromSLURM_SCONTROL_RESUME_FAILED_STATEso failing nodes are counted and protected mode triggers at the configured threshold.Tests
Checklist
developadd the branch name as prefix in the PR title (e.g.[release-3.6]).Please review the guidelines for contributing and Pull Request Instructions.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.