cannot move cloudinit to a new storage from gui

[Pca]

in proxmox 6.4

the cloudinit drive cannot be moved from the gui : the button is greyed out


if I use the CLI to move the drive to a new storage it works but I have an error at end of processing

root@pmx [~]: qm move_disk 258 ide0 newstorage
create full clone of drive ide0 (oldstorage:vm-258-cloudinit)
  Logical volume "vm-258-cloudinit" created.
Use of uninitialized value $completion in string eq at /usr/share/perl5/PVE/QemuServer.pm line 7252.

 

[bbgeek17]

Cloud-init is a disposable disk, it is regenerated on each VM start and is not used once VM is running. The move from UI is not supported in either 6.x or 7.x PVE. You should just remove and re-add it with your target storage. You can also force-regenerate it from UI afterwards.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Pca]

That's cristal clear. Thanks.

 

[Pca]

humm strange
for most vms, I can delete the drive, then immediately add a cloudinit drive again then regenerate the image, so I dont loose the cloudinit parameters.

But for some other vms, when I remove cloudinit it stays in pending remove
Fortunatly then I can cancel the remove by regenerating the image.

so for those vms I cannot modify the storage of this drive without shuting the vm down and so I will loose the cloudinit infos.

 

[bbgeek17]

It could be a specific VM type/hardware related. This thread explains the "pending" state:
https://forum.proxmox.com/threads/hw-changes-stay-orange.83517/

In general, I would use CLI to save, remove, re-add the CI as needed.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Pca]

I did some testing. As the cloudinit drive is IDE related it is in busy state in a running VM so cannot be suppressed online and is pending.
So the correct action is :
- stop the VM
- suppress cloudinit drive
- immediatly recreate it on the desired storage
- restart

and so the parameters are not lost.

But the VM should be stopped which is really a pain in a production environnement.