Corosync error and ha detection error after removing 1 node in cluster.

DuyQuy

Member
Apr 26, 2022
17
0
6
Hi all.

I have previously removed 1 node from the cluster, but recently we noticed that HA is giving an error (unable to read lrm status)

1660123680355.png

When I switched to check corosync, I noticed that they misdetected its own node ID information. For example. node ID:04 but its corosync is receiving ID:11 resulting in ID:04 disconnected.

1660123952871.png

This wrong detection of localhost information only happens on some nodes, I think that is the cause of HA failure. Is there any way to deal with that?
 
which version are you running? pveversion -v
 
I running on version pve-manager: 6.3-6 and corosync: 3.1.2-pve1.

This is output "pveversion -v"

proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.2-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-9
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.3-1
proxmox-backup-client: 1.1.1-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.5-1
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-5
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-10
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1
I make sure that the deleted node can no longer be found at /etc/pve/corosync.conf and ha-manager status
 
please update to the latest 6.4 and then 7.x - 6.4 is EOL, and your versions of corosync and kronosnet (the software underpinning our cluster stack) are outdated versions with known bugs.