[SOLVED] Cloning images to Ceph pool fails after updates

E

entith

New Member
Jul 8, 2024
3
1
3
I have a cluster of 3 PVE nodes with a Ceph pool hosted between them for VM and container disk images. I recently updated from PVE 7 to 8 and Ceph Pacific to Reef.

Specifically, I did the following:
  • Update PVE to the latest v7
  • Update Ceph from Pacific to Quincy as per the wiki instructions
  • Update PVE to v8 as per the wiki instruction
  • Update Ceph from Quincy to Reef as per the wiki instructions
The updates seemed to go off without any problems and all my VMs and containers are running with no issues.


Today I tried cloning a VM for the first time since the update and I got the following error:

Code: 
qemu-img: Could not open 'zeroinit:rbd:ceph-images/vm-119-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/ceph-images.keyring': Could not open 'rbd:ceph-images/vm-119-disk-0:conf=/etc/pve/ceph.conf:id=admin:keyring=/etc/pve/priv/ceph/ceph-images.keyring': No such file or directory

vm-119 is the target new VM, but I have tried this with several source VMs and a few different target VM IDs. I also get the same exact error when I try to move a disk image from another storage to the ceph-images rbd storage.

I am able to create new VMs and new disks for existing VMs without issue. I am also able to migrate VMs between nodes without issue. And I was able to clone VMs prior to the update.

The Pacific to Quincy migration docs mention a possible issue with "device_health_metrics" pools, but that does not appear to be the case here.

Any help with this would be really appreciated
 
Thanks! Not sure how I missed that thread from Saturday, but downgrading to pve-qemu-kvm:amd64=8.2.2-1 did the trick

For anyone else coming across this, you can downgrade to that specific version with:
apt install pve-qemu-kvm:amd64=8.2.2-1

And for completeness, the output of pveversion -v pre-downgrade:

Code: 
root@pve01:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.8-2-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
pve-kernel-5.15: 7.4-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
proxmox-kernel-6.8: 6.8.8-2
proxmox-kernel-6.8.8-2-pve-signed: 6.8.8-2
pve-kernel-5.4: 6.4-4
pve-kernel-5.15.158-1-pve: 5.15.158-1
pve-kernel-5.15.107-2-pve: 5.15.107-2
pve-kernel-5.15.83-1-pve: 5.15.83-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-1-pve: 5.11.22-2
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph: 18.2.2-pve1
ceph-fuse: 18.2.2-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown: residual config
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.1
libpve-guest-common-perl: 5.1.3
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
libqb0: 1.0.5-1
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.4.2
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.2
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.12-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.0-5
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.1
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1
 
  • Like
Reactions: Neobin
You must log in or register to reply here.
Top Bottom