Skip to content
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

fix: Allow open-vm-tools to wait indefinitely for cloud-init to finish #1203

Merged
merged 1 commit into from
Oct 14, 2024

Conversation

dlipovetsky
Copy link
Collaborator

What problem does this PR solve?:
The default timeout is 30s. At that point, open-vm-tools restarts the machine, interrupting the cloud-init bootstrap; the bootstrap does not run on reboot.

Because kubeadm init/join runs as a cloud-init command, and can run over 5m, the timeout is not enough.

Which issue(s) does this PR fix?:

Special notes for your reviewer:

Does this PR introduce a user-facing change?:


The default timeout is 30s. At that point, open-vm-tools restarts the
machine, interrupting the cloud-init bootstrap; the bootstrap does not
run on reboot.

Because kubeadm init/join runs as a cloud-init command, and can run over
5m, the timeout is not enough.
@github-actions github-actions bot added the fix label Oct 11, 2024
@dlipovetsky dlipovetsky added the runs-vsphere-tests runs the vsphere e2e tests label Oct 14, 2024
@dlipovetsky
Copy link
Collaborator Author

I built images for our VCD environment: https://github.com/mesosphere/konvoy-image-builder/actions/runs/11300000631. I verified the images with konvoy2: https://github.com/mesosphere/konvoy2/actions/runs/11300313745/job/31432960422. I saw no isseus during bootstrapping.

Copy link
Contributor

@dkoshkin dkoshkin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@supershal
Copy link
Collaborator

Great finding an effective fix.

Copy link
Collaborator

@faiq faiq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this also affect VSphere templates and not just capvcd?

@dlipovetsky
Copy link
Collaborator Author

does this also affect VSphere templates and not just capvcd?

Yes, this does affect vSphere templates. However, only cloud-init is used by the bootstrap on vSphere (CAPV); open-vm-tools is only used by the bootstrap on VCD.

@dlipovetsky dlipovetsky merged commit a39cd97 into main Oct 14, 2024
35 checks passed
@dlipovetsky dlipovetsky deleted the dlipovetsky/fix-vmware-cloudinit-timeout branch October 14, 2024 17:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix runs-vsphere-tests runs the vsphere e2e tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants