Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRAYSAT-1948: Fix traceback in sat swap blade #303

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

haasken-hpe
Copy link
Contributor

@haasken-hpe haasken-hpe commented Dec 16, 2024

Summary and Scope

Fix a traceback that occurs in sat swap blade when the node classes reported by HSM includes both "Mountain" and "Hill" for a single blade.

This probably indicates some sort of configuration problem in HSM, but the behavior of sat swap blade is the same for both Mountain and Hill, so we can log a warning and proceed in this case.

Issues and Related PRs

Testing

Tested on:

  • Local development environment

Test description:

Unit tested only so far.

Risks and Mitigations

Introduces some risk to the sat swap blade command, but unit tests are pretty good for the modified blade_class property.

Still needs to be tested on a system.

Pull Request Checklist

  • Version number(s) incremented, if applicable
  • Copyrights updated
  • License file intact
  • Target branch correct
  • CHANGELOG.md updated
  • Testing is appropriate and complete, if applicable
  • HPC Product Announcement prepared, if applicable

CHANGELOG.md Outdated Show resolved Hide resolved
sat/cli/swap/blade.py Outdated Show resolved Hide resolved
@haasken-hpe haasken-hpe force-pushed the CRAYSAT-1948-fix-blade-swap branch from 60cf7c8 to 139cedd Compare December 17, 2024 16:56
Copy link
Contributor

@ethanholen-hpe ethanholen-hpe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 👍🏻

Fix a traceback that occurs in `sat swap blade` when the node classes
reported by HSM includes both "Mountain" and "Hill" for a single blade.

This probably indicates some sort of configuration problem in HSM, but
the behavior of `sat swap blade` is the same for both Mountain and Hill,
so we can log a warning and proceed in this case.

Test Description:
Existing and new unit tests validate the new logic in `blade_class`
property.

Tested the `sat swap blade --action disable` command on baldar, which
was exhibiting the issue where a single blade had some nodes reporting
as "Hill" and some as "Mountain" in HSM. The command worked as expected.
@haasken-hpe haasken-hpe force-pushed the CRAYSAT-1948-fix-blade-swap branch from 139cedd to 5cae513 Compare December 18, 2024 22:35
@haasken-hpe
Copy link
Contributor Author

The build of cray-sat from this branch was tested by Faiyaz on baldar today with the sat swap blade --action disable command, and it succeeded. This should be sufficient testing for this change as that exercises the new logic in the BladeSwapProcedure.run method. The unit tests thoroughly test the new logic in the BladeSwapProcedure.blade_class property.

@haasken-hpe haasken-hpe merged commit 4ca53d5 into main Dec 18, 2024
3 checks passed
@haasken-hpe haasken-hpe deleted the CRAYSAT-1948-fix-blade-swap branch December 18, 2024 22:43
@haasken-hpe
Copy link
Contributor Author

/backport release/3.33

Copy link

Backporting into branch release/3.33 was successful. New PR: #308

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants