Fix missing volume in the IT node #293
Merged
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
|
@bgruening, please check with Marie to see if we can relaunch this. If she is okay with it, then we need to drain the node and delete it. Deploy this change. |
bgruening
approved these changes
Apr 11, 2024
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.
I'm sorry for the oversight. I did not notice it was missing when I created the PR this morning. An unnecessary new line split the volume section from the VM, resulting in the oversight.
As a result, the IT node depleted its storage, and new GxITs could not spawn, complaining no storage was available.
User error:
I don't think the script can dynamically mount it. The IT node must be recreated to attach a volume, as certain tasks must run in the cloud-init step.