[SOLVED] Unable to migrate VM after Removal of one of the Ring

ermanishchawla

Well-Known Member
Mar 23, 2020
332
37
48
38
Dear All,

I have two rings configured in the corosync network and I have to remove the ring configuration for one of the ring but after removal of the ringid, I am no longer able to migrate VM to each other

proxmox-ve: 6.2-1 (running kernel: 5.4.60-1-pve)


pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)


pve-kernel-5.4: 6.2-6


pve-kernel-helper: 6.2-6


pve-kernel-5.0: 6.0-11


pve-kernel-5.4.60-1-pve: 5.4.60-2


pve-kernel-5.4.44-2-pve: 5.4.44-2


pve-kernel-5.0.21-5-pve: 5.0.21-10


pve-kernel-5.0.15-1-pve: 5.0.15-1


ceph: 14.2.11-pve1


ceph-fuse: 14.2.11-pve1


corosync: 3.0.4-pve1


criu: 3.11-3


glusterfs-client: 5.5-3


ifupdown: residual config


ifupdown2: 3.0.0-1+pve2


ksm-control-daemon: 1.3-1


libjs-extjs: 6.0.1-10


libknet1: 1.16-pve1


libproxmox-acme-perl: 1.0.5


libpve-access-control: 6.1-2


libpve-apiclient-perl: 3.0-3


libpve-common-perl: 6.2-2


libpve-guest-common-perl: 3.1-3


libpve-http-server-perl: 3.0-6


libpve-storage-perl: 6.2-6


libqb0: 1.0.5-1


libspice-server1: 0.14.2-4~pve6+1


lvm2: 2.03.02-pve4


lxc-pve: 4.0.3-1


lxcfs: 4.0.3-pve3


novnc-pve: 1.1.0-1


proxmox-mini-journalreader: 1.1-1


proxmox-widget-toolkit: 2.2-12


pve-cluster: 6.1-8


pve-container: 3.2-1


pve-docs: 6.2-5


pve-edk2-firmware: 2.20200531-1


pve-firewall: 4.1-2


pve-firmware: 3.1-3


pve-ha-manager: 3.1-1


pve-i18n: 2.2-1


pve-qemu-kvm: 5.1.0-2


pve-xtermjs: 4.7.0-2


qemu-server: 6.2-14


smartmontools: 7.1-pve2


spiceterm: 3.1-1


vncterm: 1.6-2


zfsutils-linux: 0.8.4-pve1














Cluster information


-------------------


Name: INDC


Config Version: 26


Transport: knet


Secure auth: on


Quorum information


------------------


Date: Sun Sep 20 11:54:01 2020


Quorum provider: corosync_votequorum


Nodes: 12


Node ID: 0x00000002


Ring ID: 1.5cef


Quorate: Yes


Votequorum information


----------------------


Expected votes: 12


Highest expected: 12


Total votes: 12


Quorum: 7


Flags: Quorate





Membership information


----------------------


Nodeid Votes Name


0x00000001 1 172.19.2.10


0x00000002 1 172.19.2.11 (local)


0x00000003 1 172.19.2.12


0x00000004 1 172.19.2.13


0x00000005 1 172.19.2.7


0x00000006 1 172.19.2.8


0x00000007 1 172.19.2.9


0x00000008 1 172.19.2.6


0x00000009 1 172.19.2.52


0x0000000a 1 172.19.2.53


0x0000000b 1 172.19.2.55


0x0000000c 1 172.19.2.54

Error as observed

TASK ERROR: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=inc1pve3' root@172.19.1.13 pvecm mtunnel -migration_network 172.19.2.11/24 -get_migration_ip' failed: exit code 255


Please note 172.19.1.X was old ringId which is removed
 
Just an update, I am able to migrate VM from inc1pve3 to inc1pve1 but not from inc1pve1 to inc1pve3
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!