destroy_cloud_config_vdi_after_boot deletes the cloud config VDI too soon

[wkleinhenz]

Currently Im using cloud config files to bootstrap a VM Image created using packer. this is mainly being used to set host specific things like the network configuration and host name. when using
destroy_cloud_config_vdi_after_boot = true, the expected_ip_cidr setting and the default power_state setting which i believe is Running the cloud config VDI is deleted as soon as it meets the running state, but this means that the VM isn't able to access the cloud config files.

Proposed changes:

• have the provider wait a configurable number of seconds before deleting the cloud config VDI after it reaches the running state
• have the provider wait a configurable number of seconds before deleting the cloud config VDI after the expected_ip_cidr returns that the VM is ready

[vortemid]

We are experiencing this as well after upgrade XOA to version 5.101. I think the proposed changes makes sense.

[olivierlambert]

Thanks for the report. Let me ping people internally to take a look ASAP!

[ghost]

any update on the issue ?

[olivierlambert]

We have someone coming in January to take care of this, until then I'll check if someone else can take a look.

[olivierlambert]

Note: if you have pro support, creating a ticket will help to make sure we won't overlook it.

[emuchogu]

Same here - this used to work, but then the VM would not boot when created, or would boot but no cloud-init would have been applied. Commenting out the following fixed the issues, but the cloud-init disk remains attached:

destroy_cloud_config_vdi_after_boot = true

[olivierlambert]

Okay so the issue is in XO, not in the provider. Thanks for the report, we'll fix that ASAP.

For reference: vatesfr/xen-orchestra#8219