CASMPET-7448 add documentation for booting storage node into new image #5846
+151
−0
Conversation
This file contains 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
leliasen-hpe
requested review from
rustydb,
haroldlongley,
nrockershousen,
shunr-hpe,
GunashekarKM,
SavioJoshua,
sfkramer,
brookshire,
kkelling-hpe and
don-bahls-hpe
leliasen-hpe
force-pushed
the
CASMPET-7448
branch
from
65d7342 to
fde03b3
Compare
troubleshooting/known_issues/storage_node_cloud_init_fails_with_timed_out.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Nathan Rockershousen <[email protected]> Signed-off-by: Lindsay Eliasen <[email protected]>
nrockershousen
approved these changes
Mar 28, 2025
rustydb
approved these changes
Mar 28, 2025
3 tasks
…mage version after attempted upgrade
… storage node upgrade workflow
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
This PR adds documentation for booting a storage node into a new image outside of CSM upgrade. This is necessary when booting a storage node into a newly built image. This only impacts CSM 1.6 and CSM 1.5.
I have tested this procedure on Drax.
Checklist
.github/CODEOWNERSwith the corresponding team in Cray-HPE.