[ClusterLabs] the PAF switchover does not happen if the VIP resource is stopped

[范国腾]

Hi,



Our lab has two resource: (1) PAF (master/slave)    (2) VIP (bind to the master PAF node). The configuration is in the attachment.

Each node has two network card: One(enp0s8) is for the pacemaker heartbeat in internal network, the other(enp0s3) is for the master VIP in the external network.



We are testing the following case: if the master VIP network card is down, the master postgres and VIP could switch to another node.



1. At first, node2 is master, I run "ifdown enp0s3" in node2, then node1 become the master, that is ok.



[cid:image001.png at 01D3DCB4.E6FC6140]



[cid:image002.png at 01D3DCB5.4DF4DA80]



2. Then I run "ifup enp0s3" in node2, wait for 60 seconds, then run "ifdown enp0s3" in node1, but the node1 still be master. Why does switchover doesn't happened? How to recover to make system work?

[cid:image003.png at 01D3DCB5.AC487F60]



The log is in the attachment. Node1 reports the following waring:



Apr 25 04:49:27 node1 crmd[24678]:  notice: State transition S_IDLE -> S_POLICY_ENGINE

Apr 25 04:49:27 node1 pengine[24677]: warning: Processing failed op start for master-vip on sds2: unknown error (1)

Apr 25 04:49:27 node1 pengine[24677]: warning: Processing failed op start for master-vip on sds1: unknown error (1)

Apr 25 04:49:27 node1 pengine[24677]: warning: Forcing master-vip away from sds1 after 1000000 failures (max=1000000)

Apr 25 04:49:27 node1 pengine[24677]: warning: Forcing master-vip away from sds2 after 1000000 failures (max=1000000)

Apr 25 04:49:27 node1 pengine[24677]:  notice: Calculated transition 14, saving inputs in /var/lib/pacemaker/pengine/pe-input-59.bz2

Apr 25 04:49:27 node1 crmd[24678]:  notice: Transition 14 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-59.bz2): Complete




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180425/70ed7d61/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5180 bytes
Desc: image001.png
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180425/70ed7d61/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 12822 bytes
Desc: image002.png
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180425/70ed7d61/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 17027 bytes
Desc: image003.png
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180425/70ed7d61/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: info.rar
Type: application/octet-stream
Size: 6409 bytes
Desc: info.rar
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180425/70ed7d61/attachment-0001.obj>