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.

Created attachment 1276973 [details]
Reproducing PE input

Description of problem:

After fencing, PE schedules remote actions without waiting for the connection to be re-established

Version-Release number of selected component (if applicable):

everything <= 7.4

How reproducible:

100%

Steps to Reproduce:
1. crm_simulate -Sx {attachment}

Actual results:

 * Fencing controller-1 (reboot)
 * Pseudo action:   stonith_complete
 * Pseudo action:   messaging-1_stop_0
 * Pseudo action:   galera-0_stop_0
 * Pseudo action:   galera-2_stop_0
 * Resource action: galera          demote on galera-0


Expected results:

 * Fencing controller-1 (reboot)
 * Pseudo action:   stonith_complete
 * Pseudo action:   messaging-1_stop_0
 * Pseudo action:   galera-0_stop_0
 * Pseudo action:   galera-2_stop_0
 * Resource action: galera-0        start on controller-2
 * Resource action: galera          demote on galera-0

Additional info:

Just confirmed this was also the behaviour in 1.1.16

Confirmed that the problem also occurs in RHEL 7.3's 1.1.15-11.el7_3.4, but the demote is properly ordered in RHEL 6.8's 1.1.14-8.el6. So this looks like it may be a regression in 1.1.15.

Fix is:
   https://github.com/ClusterLabs/pacemaker/commit/a4e7178

Regression test is:
   https://github.com/ClusterLabs/pacemaker/commit/d3e16e0

qa_ack+:
reproducer

# crm_simulate -Sx /path/to/attachment

verify that "Resource action: galera-0 start on controller-2" happens before "Resource action: galera demote on galera-0"

without patch: fail. with patch: pass

There is no demote action tiggered because of fix in Bug 1448773 - anyway I do not see in the output of reproduce any action scheduled before starting remote connection for the remote nodes which lost their remote connection so let's move to Verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2017:1862

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days