Power off immediately if cloud-init fails #638
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
|
Darn, sorry I missed this @dbaggerman! |
|
This seems like a great idea. |
lox
added a commit
that referenced
this pull request
Nov 4, 2019
Power off immediately if cloud-init fails
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.
This appears to fix #572 for us.
We see occasional failures from
cloud-initfailing to communicate with the EC2 metadata endpoint. These appear in systemd as a failure of thecloud-finalservice. By addingOnFailure=poweroff.target, the instance will power itself off when this occurs and allow the ASG to replace it instead of hanging around in a hung state forever.