Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
This is a Red Hat OpenStack Platform 13 environment.
In this environment, there are 3 cluster nodes (Controller nodes) and 6 remote node (Compute node).
This environment has the below STONITH levels for a remote node.
~~~
Target: Hostname6
Level 1 - stonith-fence_kdump-0000000000aa,stonith-fence_compute-fence-nova
Level 2 - stonith-fence_ipmi-diag-0000000000aa,stonith-fence_kdump-0000000000aa,stonith-fence_compute-fence-nova
Level 3 - stonith-fence_ipmilan-0000000000aa,stonith-fence_compute-fence-nova
~~~
My customer tested fencing by "pcs stonith fence Hostname6", and fencing succeeded as below.
~~~
Fencing History:
* unfencing of Hostname6 successful: delegate=controller0, client=crmd.761778, origin=controller0,
completed='Mon Jul 4 16:15:18 2022'
* reboot of Hostname6 successful: delegate=controller1, client=stonith_admin.615233, origin=controller1,
completed='Mon Jul 4 16:13:13 2022'
~~~
However, after fencing, `compute-unfence-trigger` resource status become FAILED (blocked) and the remote node reboots repeatedly.
`compute-unfence-trigger_stop_0` failed due to "'unknown' (189)" error.
~~~
Clone Set: compute-unfence-trigger-clone [compute-unfence-trigger]
compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname1
compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname2
compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname3
compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname4
compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname5
compute-unfence-trigger (ocf::pacemaker:Dummy): FAILED Hostname6 (blocked)
Failed Resource Actions:
* compute-unfence-trigger_stop_0 on Hostname6 'unknown' (189): call=16, status=Error, exitreason='',
last-rc-change='Mon Jul 4 16:15:19 2022', queued=0ms, exec=0ms
Version-Release number of selected component (if applicable):
~~~
I found a similar bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1704870.
Apparently, the same issue is occurring even though the fixed version (pacemaker-1.1.23-1.el7_9.1.x86_64) is used.
How reproducible:
My customer hits this issue with the setting below.
Steps to Reproduce:
1. Configure STONITH with reference to https://access.redhat.com/solutions/1480813
~~~
Target: Hostname6
Level 1 - stonith-fence_kdump-0000000000aa,stonith-fence_compute-fence-nova
Level 2 - stonith-fence_ipmi-diag-0000000000aa,stonith-fence_kdump-0000000000aa,stonith-fence_compute-fence-nova
Level 3 - stonith-fence_ipmilan-0000000000aa,stonith-fence_compute-fence-nova
~~~
2. test fencing by the following command
# pcs stonith fence Hostname6
Actual results:
`compute-unfence-trigger` resource status become "FAILED (blocked)".
The remote node reboots repeatedly.
Expected results:
`compute-unfence-trigger` resource status become "Started".
The remote node reboots only once by fencing.
This issue is believed to affect only RHEL 7 clusters, and only when fencing is manually initiated (such as via "pcs stonith fence"). Given the status of the life cycle, this will not be fixed in RHEL 7. Upgrading to RHEL 8 or later should avoid the issue.
If there is sufficient reason to address this in RHEL 7, a backport of commit efc639cc83 would be worth testing.
Comment 20Red Hat Bugzilla
2023-09-23 04:25:44 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Description of problem: This is a Red Hat OpenStack Platform 13 environment. In this environment, there are 3 cluster nodes (Controller nodes) and 6 remote node (Compute node). This environment has the below STONITH levels for a remote node. ~~~ Target: Hostname6 Level 1 - stonith-fence_kdump-0000000000aa,stonith-fence_compute-fence-nova Level 2 - stonith-fence_ipmi-diag-0000000000aa,stonith-fence_kdump-0000000000aa,stonith-fence_compute-fence-nova Level 3 - stonith-fence_ipmilan-0000000000aa,stonith-fence_compute-fence-nova ~~~ My customer tested fencing by "pcs stonith fence Hostname6", and fencing succeeded as below. ~~~ Fencing History: * unfencing of Hostname6 successful: delegate=controller0, client=crmd.761778, origin=controller0, completed='Mon Jul 4 16:15:18 2022' * reboot of Hostname6 successful: delegate=controller1, client=stonith_admin.615233, origin=controller1, completed='Mon Jul 4 16:13:13 2022' ~~~ However, after fencing, `compute-unfence-trigger` resource status become FAILED (blocked) and the remote node reboots repeatedly. `compute-unfence-trigger_stop_0` failed due to "'unknown' (189)" error. ~~~ Clone Set: compute-unfence-trigger-clone [compute-unfence-trigger] compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname1 compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname2 compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname3 compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname4 compute-unfence-trigger (ocf::pacemaker:Dummy): Started Hostname5 compute-unfence-trigger (ocf::pacemaker:Dummy): FAILED Hostname6 (blocked) Failed Resource Actions: * compute-unfence-trigger_stop_0 on Hostname6 'unknown' (189): call=16, status=Error, exitreason='', last-rc-change='Mon Jul 4 16:15:19 2022', queued=0ms, exec=0ms Version-Release number of selected component (if applicable): ~~~ I found a similar bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1704870. Apparently, the same issue is occurring even though the fixed version (pacemaker-1.1.23-1.el7_9.1.x86_64) is used. How reproducible: My customer hits this issue with the setting below. Steps to Reproduce: 1. Configure STONITH with reference to https://access.redhat.com/solutions/1480813 ~~~ Target: Hostname6 Level 1 - stonith-fence_kdump-0000000000aa,stonith-fence_compute-fence-nova Level 2 - stonith-fence_ipmi-diag-0000000000aa,stonith-fence_kdump-0000000000aa,stonith-fence_compute-fence-nova Level 3 - stonith-fence_ipmilan-0000000000aa,stonith-fence_compute-fence-nova ~~~ 2. test fencing by the following command # pcs stonith fence Hostname6 Actual results: `compute-unfence-trigger` resource status become "FAILED (blocked)". The remote node reboots repeatedly. Expected results: `compute-unfence-trigger` resource status become "Started". The remote node reboots only once by fencing.