-
Notifications
You must be signed in to change notification settings - Fork 6
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
cloud-init does not complete installs #2
Comments
Hey @jeremycolson Glad you found it useful 😄 It's been a while since I used this but I seem to remember a race condition where the cloud init installation took longer than the registration with ADO. This was a one time issue though IIRC? Once it has provisioned then the VM sits there ready to go for next time. Let me know if this chimes with you or if I've missed something. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First, awesome repo @matt-FFFFFF ... Found this extremely helpful when learning how to deploy VMSS ala Bicep.
What I've come to realize is the ado pipeline will pick-up an instance/agent before cloud-init has completed the post-deployment installations. I thought about incorporating cloud-init status --wait to ensure the pipeline does not progress until cloud-init completes the post-deployment tasks, but that's pretty messy. Every pipeline would need this noise... And the next stage could pick up a totally different instance/agent (let's say one that has not completed the cloud-init).
While not directly related to this repo (everything works beautifully), have you run into this issue before? Curious what your solution was to this dilemma. Thanks for your contributions!
The text was updated successfully, but these errors were encountered: