bug(cloudinit): do not call cloudinit stages.Init when disabled #1923
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
dbungert
reviewed
Mar 1, 2024
blackboxsw
force-pushed
the
cloudinit-no-init-when-disabled
branch
3 times, most recently
from
ee45667
to
dddb441
Compare
Inspect cloud-init status for disabled. When disabled do not call stages.Init due to a side-effect that cloud-init tries to rediscover any viable datasource when none are previously discovered. LP: #2055077
blackboxsw
force-pushed
the
cloudinit-no-init-when-disabled
branch
from
dddb441
to
972e0d5
Compare
dbungert
approved these changes
Mar 2, 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.
Inspect cloud-init status for disabled. When disabled do not call stages.Init due to a side-effect that cloud-init tries to rediscover any viable datasource when none are previously discovered.
LP: #2055077