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:

Pacemaker/systemd integration leaves much to be desired when the admin types 'reboot' without first stopping the cluster.


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

All

How reproducible:

100%


Steps to Reproduce:
1. Add systemd resources to the cluster
2. Type reboot
3.

Actual results:

systemd will allow systemd resources started by the cluster to shut down before the cluster.  If you're unlucky, systemd will also take out the dlm from underneath the cluster causing the node to be fenced.

Expected results:

The cluster is asked to shut down first and co-ordinates the shutdown of systemd resources while observing ordering constraints.

Additional info:

Patches list:

+ Andrew Beekhof 2ab97ec: Fix: systemd: Trick systemd into not stopping our services before us during shutdown 
+ Andrew Beekhof 0315c57: Fix: systemd: Kindly ask dbus NOT to kill the process if the dbus connection fails 
+ Andrew Beekhof 90d725d: Fix: systemd: Tell systemd not to take DBus down from underneath us

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://rhn.redhat.com/errata/RHSA-2015-2383.html