[PATCH 2/2] crm-fence-peer.9.sh: use join of node_state to judge whether node is banned
Su Yue <[email protected]>
| Newsgroups | dev.linux.lists.drbd-dev |
|---|---|
| Message-ID | <[email protected]> |
From: Su Yue <[email protected]> crmd in node_state can't be "banned". join should be used instead of crmd. Signed-off-by: Su Yue <[email protected]> --- scripts/crm-fence-peer.9.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/crm-fence-peer.9.sh b/scripts/crm-fence-peer.9.sh index a3353a7354a6..b326a1656c15 100755 --- a/scripts/crm-fence-peer.9.sh +++ b/scripts/crm-fence-peer.9.sh @@ -934,7 +934,7 @@ guess_if_pacemaker_will_fence() # for further inspiration, see pacemaker:lib/pengine/unpack.c, determine_online_status_fencing() [[ -z $in_ccm ]] && will_fence=true - [[ $crmd = "banned" ]] && will_fence=true + [[ $join = "banned" ]] && will_fence=true if [[ ${expected-down} = "down" && $in_ccm = "false" && $crmd != "online" ]]; then : "pacemaker considers this as clean down" elif [[ $in_ccm = false ]] || [[ $crmd != "online" ]]; then -- 2.44.0