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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add config parameter to wait for cloud-init (Extensions.WaitForCloudInit) #3031
Add config parameter to wait for cloud-init (Extensions.WaitForCloudInit) #3031
Changes from 5 commits
3e71257
c57ca48
c5dae00
eaff3bc
15f1385
e709af0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On my PR for updating the daemon to clean up any stale files if VM image was not properly generalized, we discussed the possibility that agent and cloud-init will be racing (since the agent will detect that the vm is in a 'provisioned' state when it is not).
Could we add a call to _wait_for_cloud_init() in the daemon to protect against this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The race I was mentioning is against the Config stage, that is where the Azure module does the provisioning stuff. The wait I am adding is against the Final stage. PA does not wait for Final because there could be lengthy operations there that could affect TDPR (that is why the option I added needs to be explicitly set on a custom image).
Waiting for Config when 'provisioned' exists may be a good idea, but I would leave the decision of whether to implement it to PA.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes sense