Ver 5.2 Migration fail post upgrade

[Gastondc]

Dear,

I just migrated from version 4.4 to version 5.5. Everything went perfect. Previously reading in this forum I read that there were no problems of cluster compatibility between these versions.

But I have a problem to migrate CT and VM of the node with see 5.5 to 4.4 (not so in reverse, from 4.4 to 5.5 migrates without problem)

I copy the error message, can you guide me to review more?

root@pmx02:~# pct migrate 102 pve
2018-05-29 00:17:30 starting migration of CT 102 to node 'pve' (192.168.48.10)
2018-05-29 00:17:30 found local volume 'local-zfs:subvol-102-disk-1' (in current VM config)
ERROR: unknown command 'import'
USAGE: pvesm <COMMAND> [ARGS] [OPTIONS]
pvesm add <type> <storage> [OPTIONS]
pvesm remove <storage>
full send of rpool/data/subvol-102-disk-1@__migration__ estimated size is 936M
total estimated size is 936M
pvesm set <storage> [OPTIONS]

pvesm alloc <storage> <vmid> <filename> <size> [OPTIONS]
pvesm free <volume> [OPTIONS]
pvesm list <storage> [OPTIONS]

pvesm glusterfsscan <server>
pvesm iscsiscan -portal <string> [OPTIONS]
pvesm lvmscan
pvesm lvmthinscan <vg>
pvesm nfsscan <server>
pvesm zfsscan

pvesm status [OPTIONS]

pvesm extractconfig <volume>
pvesm path <volume>

pvesm help [<cmd>] [OPTIONS]
TIME SENT SNAPSHOT
command 'zfs send -Rpv -- rpool/data/subvol-102-disk-1@__migration__' failed: got signal 13
send/receive failed, cleaning up snapshot(s)..
2018-05-29 00:17:33 ERROR: command 'set -o pipefail && pvesm export local-zfs:subvol-102-disk-1 zfs - -with-snapshots 0 -snapshot __migration__ | /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve' root@192.168.48.10 -- pvesm import local-zfs:subvol-102-disk-1 zfs - -with-snapshots 0 -delete-snapshot __migration__' failed: exit code 255
2018-05-29 00:17:33 aborting phase 1 - cleanup resources
2018-05-29 00:17:33 ERROR: found stale volume copy 'local-zfs:subvol-102-disk-1' on node 'pve'
2018-05-29 00:17:33 start final cleanup
2018-05-29 00:17:33 ERROR: migration aborted (duration 00:00:03): command 'set -o pipefail && pvesm export local-zfs:subvol-102-disk-1 zfs - -with-snapshots 0 -snapshot __migration__ | /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=pve' root@192.168.48.10 -- pvesm import local-zfs:subvol-102-disk-1 zfs - -with-snapshots 0 -delete-snapshot __migration__' failed: exit code 255
migration aborted



can you guide me to review more?

​

 

[Gastondc]

node 5.2

root@pmx02:~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.17-2-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-2
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.4.128-1-pve: 4.4.128-111
pve-kernel-4.4.79-1-pve: 4.4.79-95
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.62-1-pve: 4.4.62-88
pve-kernel-4.4.35-1-pve: 4.4.35-77
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-9
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

node 4.4

root@pve:~# pveversion -v
proxmox-ve: 4.4-94 (running kernel: 4.4.62-1-pve)
pve-manager: 4.4-18 (running version: 4.4-18/ef2610e8)
pve-kernel-4.4.19-1-pve: 4.4.19-66
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.62-1-pve: 4.4.62-88
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-52
qemu-server: 4.0-112
pve-firmware: 1.1-11
libpve-common-perl: 4.0-96
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-101
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

 

[dietmar]

Yes, migrate from new to old nodes may fail. We only make sure that you can migrate from old to new nodes.

 

[Gastondc]

Yes, migrate from new to old nodes may fail. We only make sure that you can migrate from old to new nodes.

Thank you very much for the quick answer.

To survive while we are migrating: Is there a way to migrate manually by console until you update the node with 4.4?