Open ivicavujovic opened 6 months ago
this is bug
Thanks for your bug report. This is definitely not supposed to happen.
Could you please report the output of corosync-quorumtool -p
on both nodes?
Yes, here is the output from all three nodes:
root@node1:~# corosync-quorumtool -p
Quorum information
------------------
Date: Tue Mar 5 14:11:15 2024
Quorum provider: corosync_votequorum
Nodes: 3
Node ID: 1
Ring ID: 1.149
Quorate: Yes
Votequorum information
----------------------
Expected votes: 3
Highest expected: 3
Total votes: 3
Quorum: 2
Flags: Quorate
Membership information
----------------------
Nodeid Votes Qdevice Name
1 1 NR node1.infra.env (local)
2 1 NR XXXX:YYYY:ZZZZ:QQQQ::62%32695
3 1 NR XXXX:YYYY:ZZZZ:QQQQ::63%32695
root@node2:~# corosync-quorumtool -p
Quorum information
------------------
Date: Tue Mar 5 14:11:56 2024
Quorum provider: corosync_votequorum
Nodes: 3
Node ID: 2
Ring ID: 1.149
Quorate: Yes
Votequorum information
----------------------
Expected votes: 3
Highest expected: 3
Total votes: 3
Quorum: 2
Flags: Quorate
Membership information
----------------------
Nodeid Votes Qdevice Name
1 1 NR XXXX:YYYY:ZZZZ:QQQQ::61%32620
2 1 NR node2.infra.env (local)
3 1 NR XXXX:YYYY:ZZZZ:QQQQ::63%32620
root@node3:~# corosync-quorumtool -p
Quorum information
------------------
Date: Tue Mar 5 14:12:31 2024
Quorum provider: corosync_votequorum
Nodes: 3
Node ID: 3
Ring ID: 1.149
Quorate: Yes
Votequorum information
----------------------
Expected votes: 3
Highest expected: 3
Total votes: 3
Quorum: 2
Flags: Quorate
Membership information
----------------------
Nodeid Votes Qdevice Name
1 1 NR XXXX:YYYY:ZZZZ:QQQQ::61%32728
2 1 NR XXXX:YYYY:ZZZZ:QQQQ::62%32728
3 1 NR node3.infra.env (local)
Thanks, I will look into it sometime over the coming weeks and let you know.
Thanks a lot for the effort.
Hi, we have several three-node clusters with the Corosyc/Pacemaker setup. There is a ha_cluster_exporter set on all of them, and it works just fine. Only on one node in one cluster, we get an error like this when I open the metrics URL:
I checked all nodes in the cluster, and all of them have different IDs:
Logs are very similar on all of the nodes:
All nodes have the same configuration (OS, HDD, RAM, CPU) and are built and provisioned using Puppet configuration management.
Service file is very simple:
For the love of God, I cannot find what could be an issue here. Did we make some misconfiguration, or did we miss some of that? There is nothing special set; we install the exporter and run it.
OS is Debian 11, version of exporter is 1.3.3 (but same issue with older versions too).