You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Go to '...'
Click on '...'
Scroll down to '...'
See error
Expected behavior
No response
Screenshots
No response
Node
LTS
Hypervisor
8.2 and 8.3
Additional context
No response
The text was updated successfully, but these errors were encountered:
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
Expected behavior
No response
Screenshots
No response
Node
LTS
Hypervisor
8.2 and 8.3
Additional context
No response
The text was updated successfully, but these errors were encountered: