This will avoid useless fencing events in case of stonith problems. The
'compute-unfence-trigger' resource is simply a dummy resource that is
only used to trigger unfence events. If for whatever reason this
resource is having issues on stop (pcmk bug, node overloaded, etc.) it
makes zero sense to have pacemaker do a fencing action against the node.
Let's just block and show the operator the status and be less harsh in
general.
Tested this and I correctly get the following:
[root@controller-0 ~]# pcs resource show compute-unfence-trigger-clone
Clone: compute-unfence-trigger-clone
Resource: compute-unfence-trigger (class=ocf provider=pacemaker type=Dummy)
Meta Attrs: requires=unfencing
Operations: migrate_from interval=0s timeout=20 (compute-unfence-trigger-migrate_from-interval-0s) migrate_to interval=0s timeout=20 (compute-unfence-trigger-migrate_to-interval-0s) monitor interval=10 timeout=20 (compute-unfence-trigger-monitor-interval-10) reload interval=0s timeout=20 (compute-unfence-trigger-reload-interval-0s) start interval=0s timeout=20 (compute-unfence-trigger-start-interval-0s) stop interval=0s on-fail=block timeout=20 (compute-unfence-trigger-stop-interval-0s)
Closes-Bug: #1831234
Change-Id: Ib4884078d54c25da998495ba3e8d47b5e17010ce
(cherry picked from commit 8d2c3a0e6e392e2f358bf29a3b900afcd5bbe56a)
Reviewed: https:/ /review. opendev. org/665589 /git.openstack. org/cgit/ openstack/ puppet- tripleo/ commit/ ?id=a2ceac8bafe dcedae20811a78a 6ccb3823abf36d
Committed: https:/
Submitter: Zuul
Branch: stable/stein
commit a2ceac8bafedced ae20811a78a6ccb 3823abf36d
Author: Michele Baldessari <email address hidden>
Date: Tue May 28 10:50:16 2019 +0200
IHA robustness improvements
This will avoid useless fencing events in case of stonith problems. The unfence- trigger' resource is simply a dummy resource that is
'compute-
only used to trigger unfence events. If for whatever reason this
resource is having issues on stop (pcmk bug, node overloaded, etc.) it
makes zero sense to have pacemaker do a fencing action against the node.
Let's just block and show the operator the status and be less harsh in
general.
Tested this and I correctly get the following: controller- 0 ~]# pcs resource show compute- unfence- trigger- clone unfence- trigger- clone unfence- trigger (class=ocf provider=pacemaker type=Dummy) unfence- trigger- migrate_ from-interval- 0s)
migrate_ to interval=0s timeout=20 (compute- unfence- trigger- migrate_ to-interval- 0s)
monitor interval=10 timeout=20 (compute- unfence- trigger- monitor- interval- 10)
reload interval=0s timeout=20 (compute- unfence- trigger- reload- interval- 0s)
start interval=0s timeout=20 (compute- unfence- trigger- start-interval- 0s)
stop interval=0s on-fail=block timeout=20 (compute- unfence- trigger- stop-interval- 0s)
[root@
Clone: compute-
Resource: compute-
Meta Attrs: requires=unfencing
Operations: migrate_from interval=0s timeout=20 (compute-
Closes-Bug: #1831234
Change-Id: Ib4884078d54c25 da998495ba3e8d4 7b5e17010ce f358bf29a3b900a fcd5bbe56a)
(cherry picked from commit 8d2c3a0e6e392e2