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-1942: Drop internal default values for rootfs_provider{,passthrough} from sat bootprep #304

Merged
merged 1 commit into from
Dec 19, 2024

Conversation

ethanholen-hpe
Copy link
Contributor

@ethanholen-hpe ethanholen-hpe commented Dec 17, 2024

Summary and Scope

Drop internal default values for rootfs_provider{,passthrough} from sat bootprep

Issues and Related PRs

List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Testing

Tested on:

  • rocket
  • Local development environment

Test description:

  • Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
  • Were continuous integration tests run? If not, why?
  • Was upgrade tested? If not, why?
  • Was downgrade tested? If not, why?
  • Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations

Are there known issues with these changes? Any other special considerations?

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

@ethanholen-hpe
Copy link
Contributor Author

@ethanholen-hpe
Copy link
Contributor Author

@ethanholen-hpe
Copy link
Contributor Author

@ethanholen-hpe ethanholen-hpe merged commit 90d22b2 into main Dec 19, 2024
3 checks passed
@ethanholen-hpe ethanholen-hpe deleted the CRAYSAT-1942 branch December 19, 2024 17:02
@ethanholen-hpe
Copy link
Contributor Author

/backport release/3.33

Copy link

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

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.

2 participants