Sorry, it seems I miss some description here. Add them.
On 03/24/2020 11:02 AM, Pingfan Liu wrote:
There is a race issue between "pcs" and "kdumpctl
restart"
-1. set up cluster
# pcs cluster setup --start mycluster node1 node2
# pcs stonith create kdump fence_kdump pcmk_reboot_action="off"
# pcs stonith level add 1 node1 kdump
# pcs stonith level add 1 node2 kdump
-2. Then here comes the command _immediately_ in kdumpctl
# pcs cluster cib
But due to some pcs internal mechanism, "pcs cluster cib" can not
fetch the updated info in time.
Fix these issue by forcing the upgrade of cib.
Signed-off-by: Pingfan Liu <piliu(a)redhat.com>
---
dracut-module-setup.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/dracut-module-setup.sh b/dracut-module-setup.sh
index 7a2c7b4..5f91c89 100755
--- a/dracut-module-setup.sh
+++ b/dracut-module-setup.sh
@@ -712,6 +712,7 @@ is_localhost() {
get_pcs_fence_kdump_nodes() {
local nodes
+ pcs cluster sync && pcs cluster cib-upgrade
# get cluster nodes from cluster cib, get interface and ip address
nodelist=`pcs cluster cib | xmllint --xpath
"/cib/status/node_state/@uname" -`