Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 798438

Summary: sys-cluster/pacemaker-2.0.5 startup issues with sys-cluster/corosync-3.1.0
Product: Gentoo Linux Reporter: Christian R <chris>
Component: Current packagesAssignee: Gentoo Cluster Team <cluster>
Status: UNCONFIRMED ---    
Severity: normal CC: mscardovi, robbat2
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Package list:
Runtime testing required: ---

Description Christian R 2021-06-24 17:41:49 UTC
pacemaker init script checks if corosync is running with
/usr/sbin/corosync-cfgtool -s

on pacemaker-1.1.19-r1 exit code is 0 even when the second node is offline.
on pacemaker-2.0 exit code is 1 when the second node is offline.

output pacemaker-1:
gentoo ~ # /usr/sbin/corosync-cfgtool -s
Printing ring status.
Local node ID 1
        id      =
        status  = ring 0 active with no faults
gentoo ~ # echo $?

output pacemaker-2:
gentoo2 /etc/pacemaker # /usr/sbin/corosync-cfgtool -s
Printing link status.
Local node ID 2
        addr    =
                nodeid  1:      disconnected
                nodeid  2:      localhost
gentoo2 /etc/pacemaker # echo $?

corosync is running, but pacemaker does not start because exit code is 1.
i think pacemaker should start even when second node is offline.

Reproducible: Always
Comment 1 Christian R 2021-06-24 18:33:10 UTC
corosync-cfgtool outputs are from corosync 2 and 3, not pacemaker, sorry.
Comment 2 Christian R 2021-08-15 09:55:25 UTC
i did the following changes:
nano /etc/init.d/pacemaker
+               /usr/sbin/corosync-quorumtool -l &>/dev/null && break
-               /usr/sbin/corosync-cfgtool -s &>/dev/null && break