Hello,
There's a problem with cloud-init drive, when creating this drive you have the option to choose the image type as like normal disks (raw, qcow2 or vmdk) but when choosing type other than qcow2, (raw or vmdk), It will get ignored and pve will always create qcow2 format.
What is the problem with that?
This is preventing from creating a full clone of type raw when this VM is a template, because all disks are in raw format, but the cloud-init is forcibly in qcow2 format, the clone process will logically fail with error:
So please consider having a look into that.
Thanks a lot
There's a problem with cloud-init drive, when creating this drive you have the option to choose the image type as like normal disks (raw, qcow2 or vmdk) but when choosing type other than qcow2, (raw or vmdk), It will get ignored and pve will always create qcow2 format.
What is the problem with that?
This is preventing from creating a full clone of type raw when this VM is a template, because all disks are in raw format, but the cloud-init is forcibly in qcow2 format, the clone process will logically fail with error:
TASK ERROR: clone failed: unable to parse volume filename 'vm-106-cloudinit'
So please consider having a look into that.
Thanks a lot