[SOLVED] How to force a node to catch-up? config_version is behind by 1

[Dulcow]

Hi there,

I have added a new node (pve-nuc6-5) while one was offline (pve-nuc6-4). As a result, pve-nuc6-4 remains offline despite being accessible.



I noticed that pve-nuc6-4 was one version (Corosync.conf) behind the rest of the cluster.

How do I force it to sync to the last version?

Thanks,

D.

 

[Dulcow]

A working node:

root@pve-nuc6-5:~# pvecm status
Cluster information
-------------------
Name: pve-cluster
Config Version: 6
Transport: knet
Secure auth: on

Quorum information
------------------
Date: Tue Oct 3 17:37:49 2023
Quorum provider: corosync_votequorum
Nodes: 5
Node ID: 0x00000006
Ring ID: 1.d8f
Quorate: Yes

Votequorum information
----------------------
Expected votes: 6
Highest expected: 6
Total votes: 5
Quorum: 4
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.0.0.201
0x00000002 1 10.0.0.202
0x00000003 1 10.0.0.203
0x00000004 1 10.0.0.208
0x00000006 1 10.0.0.205 (local)

The offline node:

root@pve-nuc6-4:~# pvecm status
Cluster information
-------------------
Name: pve-cluster
Config Version: 5
Transport: knet
Secure auth: on

Quorum information
------------------
Date: Tue Oct 3 17:36:36 2023
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000005
Ring ID: 5.d2b
Quorate: No

Votequorum information
----------------------
Expected votes: 5
Highest expected: 5
Total votes: 1
Quorum: 3 Activity blocked
Flags:

Membership information
----------------------
Nodeid Votes Name
0x00000005 1 10.0.0.204 (local)

 

[Dulcow]

Editing /etc/corosync/corosync.conf with the last up to date configurations and restarting the service fixed the issue ;-)