Two node proxmox cluster with debian quorum mismatch

General
1

Hi,

I am trying to setup in a lab a two node proxmox server running linbit for shared storage and a separate debian system as the tie breaker. I have the two nodes up and running and started working the 3rd node for the quroum. I have it working fine with coresync, but after going through trying to add linbit I am getting a version mismatch.

Been trying to get this up and running for the last week or so and about to just give up on using linbit and try something else for the shared storage. Below is the output of the cat commands.

Node ┊ NodeType ┊ Addresses ┊ State ┊
╞════════════════════════════════════════════════════════════════════════════╡
┊ pve01 ┊ SATELLITE ┊ 10.35.15.18:3366 (PLAIN) ┊ Online ┊
┊ pve02 ┊ SATELLITE ┊ 10.35.15.19:3366 (PLAIN) ┊ Online ┊
┊ pveqdev ┊ SATELLITE ┊ 10.35.15.16:3366 (PLAIN) ┊ OFFLINE(VERSION MISMATCH) ┊

I have done a cat /proc/drdb on all the nodes and it is showing the same versions. How do I resolve this?

root@pveqdev:~# cat /proc/drbd
version: 9.2.13 (api:2/proto:118-122)
GIT-hash: 0457237e0448663529fe161781873b356f17b3c5 build by root@pveqdev, 2025-05-23 10:45:04

root@pve02:~# cat /proc/drbd
version: 9.2.13 (api:2/proto:118-122)
GIT-hash: 0457237e0448663529fe161781873b356f17b3c5 build by root@pve02, 2025-05-17 17:49:01
Transports (api:21):

root@pve01:/etc/systemd/system# cat /proc/drbd
version: 9.2.13 (api:2/proto:118-122)
GIT-hash: 0457237e0448663529fe161781873b356f17b3c5 build by root@pve01, 2025-05-05 21:20:22
Transports (api:21):

2

It’s a version mismatch of the satellite server it’s complaining about. Try dpkg-query -l linstor-satellite on each of the three nodes.

It’s possible that a newer version of linstor was released between the time you installed the first two nodes and the third node (this happened to me recently). The solution is to upgrade linstor-controller, then update linstor-satellite on the other two nodes, so all the versions match.

Linstor insists that the controller and satellites have exactly matching versions: e.g. 1.31.1 will not talk to 1.31.0, or vice versa. But upgrading is a seamless process which doesn’t cause any outage, since the drbd devices which have already been configured will be unaffected.