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

"Destroy cloud config drive after first boot" is happening too soon #8219

Open
olivierlambert opened this issue Jan 2, 2025 · 0 comments
Open
Assignees

Comments

@olivierlambert
Copy link
Member

Are you using XOA or XO from the sources?

XOA

Which release channel?

latest

Provide your commit number

No response

Describe the bug

When we enable "Destroy cloud config drive after first boot" (during VM creation in advanced section) it seems to we destroy the disk right after VM boot, which is too fast. Cloudinit needs to read the disk and apply the config first. We could also be smart: we use could a default long timer (like 5 minutes) but if we got the tools detected, we can go down for 30 secs

Error message

No response

To reproduce

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. See error

Expected behavior

No response

Screenshots

No response

Node

LTS

Hypervisor

8.2 and 8.3

Additional context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants