Comment 12 for bug 1800940

Thanks for the offer of assistance Frederik. I missed the email notification when it came through and apologise for not updating this ticket sooner.

I have been able to identify the change that has introduced this problem[0]. As context, Juju does quite a complicated dance when creating a virtual machine. We want to make sure that we're using a Ubuntu certified cloud image[1], but we also wish to enable some parameters that may be specified by configuration parameters. So we download the image, tweak some parameters in its metadata file, then upload the disk along with the new metadata to VSAN.

It looks as though the metadata file that Juju generates is incorrect and the VMDK uploaded into the vSAN does not get imported correctly. I'll update the ticket when I've discovered where the fault lies.

[0] https://github.com/juju/juju/pull/7856
[1] https://cloud-images.ubuntu.com/