[integ-tests] Fix assert_no_errors_in_logs to skip ICE-caused "setting nodes to DOWN" errors#7423
Merged
Conversation
…g nodes to DOWN" errors
When skip_ice=True, assert_no_errors_in_logs filtered log lines by matching
EC2 capacity message fragments (e.g. "InsufficientInstanceCapacity") against
each line. This caught the root-cause ERRORs, but missed the downstream ERROR:
```
ERROR - Failed to launch following nodes, setting nodes to DOWN: [...]
```
That line carries no capacity keyword or error code, so it was never filtered.
The EC2 error code only appears on the companion INFO line written by
_handle_failed_nodes ("(Code:InsufficientInstanceCapacity)Failure when
resuming nodes..."). As a result, tests calling skip_ice=True could still fail
intermittently whenever ICE struck on the dynamic-node resume path.
This change pairs the untagged "setting nodes to DOWN" ERROR with the
"(Code:<error_code>)" reasons found in the same log file. When skip_ice is set,
the line is ignored only if at least one code is present and every code in that
file is a known ICE code; otherwise the line is kept so genuine non-ICE launch
failures still fail the assertion.
The ICE code set mirrors SlurmNode.EC2_ICE_ERROR_CODES from
aws-parallelcluster-node plus LimitedInstanceCapacity (used for partial
all-or-nothing/best-effort launches).
hehe7318
approved these changes
Jun 5, 2026
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.
Description of changes
When skip_ice=True, assert_no_errors_in_logs filtered log lines by matching EC2 capacity message fragments (e.g. "InsufficientInstanceCapacity") against each line. This caught the root-cause ERRORs, but missed the downstream ERROR:
That line carries no capacity keyword or error code, so it was never filtered. The EC2 error code only appears on the companion INFO line written by _handle_failed_nodes ("(Code:InsufficientInstanceCapacity)Failure when resuming nodes..."). As a result, tests calling skip_ice=True could still fail intermittently whenever ICE struck on the dynamic-node resume path.
This change pairs the untagged "setting nodes to DOWN" ERROR with the "(Code:<error_code>)" reasons found in the same log file. When skip_ice is set, the line is ignored only if at least one code is present and every code in that file is a known ICE code; otherwise the line is kept so genuine non-ICE launch failures still fail the assertion.
The ICE code set mirrors SlurmNode.EC2_ICE_ERROR_CODES from aws-parallelcluster-node plus LimitedInstanceCapacity (used for partial all-or-nothing/best-effort launches).
Tests
References
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.