Update cloud-init behavior and iso generation #13666
Merged
+392
−99
Conversation
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
e75977e to
f3f86ae
Compare
f3f86ae to
72909ec
Compare
This includes a couple modifications to the cloud-init behavior. First, the cloud-init wait action will now write a sentinel file after successfully waiting for cloud-init. This results in subsequent boots of the machine to skip executing the cloud-init wait command as cloud-init is only executed on the initial boot. Second, the cloud-init setup action will check for the sentinel file written by the cloud-init wait action, and if detected it will skip the cloud-init setup. When creating the ISO for cloud-init, a second sentinel file will be used to log the path of the generated ISO file. If the file exists, the ISO generation process will be skipped.
72909ec to
f4fc2c7
Compare
tehut
approved these changes
May 14, 2025
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 includes a couple modifications to the cloud-init behavior.
First, the cloud-init wait action will now write a sentinel file
after successfully waiting for cloud-init. This results in subsequent
boots of the machine to skip executing the cloud-init wait command
as cloud-init is only executed on the initial boot.
Second, the cloud-init setup action will check for the sentinel file
written by the cloud-init wait action, and if detected it will skip
the cloud-init setup. When creating the ISO for cloud-init, a second
sentinel file will be used to log the path of the generated ISO
file. If the file exists, the ISO generation process will be skipped.
Fixes #13664