Found issue when cluster have several RBD(external) storage's with same pool name.
Creating, deleting rbd image works without any issue, but "move disk" or when qemu have same disk names on different storage's cause an error - proxmox doesn't understand what storage currently in use.
Moving disk to another RBD storage with same pool name:
/usr/bin/qemu-img convert -p -n -f raw -O raw /dev/rbd/rbd/vm-91123-disk-1 zeroinit:/dev/rbd/rbd/vm-91123-disk-1
Moving disk to another RBD storage with different pool name:
/usr/bin/qemu-img convert -p -n -f raw -O raw /dev/rbd/rbd/vm-91123-disk-1 zeroinit:/dev/rbd/some-ceph-pool/vm-91123-disk-1
Issue reproduces on:
pve-manager/4.1-5/f910ef5c (running kernel: 4.2.6-1-pve)
pve-manager/4.4-18/ef2610e8 (running kernel: 4.4.83-1-pve)
pve-manager/5.2-2/b1d1c7f4 (running kernel: 4.15.17-1-pve)
PS: On pve-manager/3.4-11/6502936f (running kernel: 2.6.32-41-pve) works fine.
Creating, deleting rbd image works without any issue, but "move disk" or when qemu have same disk names on different storage's cause an error - proxmox doesn't understand what storage currently in use.
Moving disk to another RBD storage with same pool name:
/usr/bin/qemu-img convert -p -n -f raw -O raw /dev/rbd/rbd/vm-91123-disk-1 zeroinit:/dev/rbd/rbd/vm-91123-disk-1
Moving disk to another RBD storage with different pool name:
/usr/bin/qemu-img convert -p -n -f raw -O raw /dev/rbd/rbd/vm-91123-disk-1 zeroinit:/dev/rbd/some-ceph-pool/vm-91123-disk-1
Issue reproduces on:
pve-manager/4.1-5/f910ef5c (running kernel: 4.2.6-1-pve)
pve-manager/4.4-18/ef2610e8 (running kernel: 4.4.83-1-pve)
pve-manager/5.2-2/b1d1c7f4 (running kernel: 4.15.17-1-pve)
PS: On pve-manager/3.4-11/6502936f (running kernel: 2.6.32-41-pve) works fine.