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.
(In reply to Reid Wahl from comment #0)
<snip>
> (log_async_result) error: Operation 'off' [1867758] targeting node2 using
> badfence returned 1 | call 2 from stonith_admin.1867754
> Jul 11 18:32:07 fastvm-rhel-8-0-23 pacemaker-fenced [1867100]
> (fenced_process_fencing_reply) notice: Action 'off' targeting node2 using
> badfence on behalf of stonith_admin.1867754@node1: complete
> Jul 11 18:32:07 fastvm-rhel-8-0-23 pacemaker-fenced [1867100]
> (undo_op_remap) info: Undoing remap of reboot targeting node2 for
> stonith_admin.1867754 | id=14c5fe89
> Jul 11 18:32:07 fastvm-rhel-8-0-23 pacemaker-fenced [1867100]
> (request_peer_fencing) notice: Requesting that node1 perform 'reboot'
> action targeting node2 using xvm | for client stonith_admin.1867754 (144s)
> Jul 11 18:32:07 fastvm-rhel-8-0-23 pacemaker-fenced [1867100]
> (log_async_result) notice: Operation 'reboot' [1867760] targeting node2
> using xvm returned 0 | call 2 from stonith_admin.1867754
It looks like the initiating node did the right thing: it asked node1 to reboot (not turn off) node2 using the xvm device. So my first thought is that either node1 somehow messed that up and executed off instead, or the xvm agent did. What do the logs on that node say?