handle degraded cloud-init as long as it set up necessary components - #181
Merged
Merged
Conversation
bjsvedin
approved these changes
Sep 1, 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
2 participants
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.
Handle degraded cloud-init completion during redeploy
Updates the Terraform redeploy wait step to handle cases where
cloud-init status --waitreturns exit code2even though provisioning has completed sufficiently for deployment.Instead of treating any non-zero exit code as a failure, the redeploy script now:
Continues normally when cloud-init exits
0.Accepts exit
2when both required deployment scripts are present and executable:/usr/local/bin/lightning-server-redeploy/usr/local/bin/lightning-server-predeployFails when cloud-init returns another error or the required scripts are missing.
This makes the redeploy process resilient to cloud-init completing in a degraded state while still verifying that the deployment prerequisites were successfully installed.