Power down non-responding node if there is not instance attached#4627
Merged
ankitkumar-quad merged 1 commit intoSep 9, 2025
Merged
Conversation
samskillman
approved these changes
Sep 8, 2025
22f1665
into
GoogleCloudPlatform:release-candidate
37 of 69 checks passed
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
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 to fix any stale
NOT_RESPONDINGflags given in the nodestate in Slurm and resetting the nodes to power down. Considered the instance is non-existant in this scenarios this shouldn't harbor any side effects for already running VMs which may correctly carry aNOT_RESPONDINGflag for other reasons.Submission Checklist
NOTE: Community submissions can take up to 2 weeks to be reviewed.
Please take the following actions before submitting this pull request.