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:
On a pacemaker-remote-node where sbd is enabled including the
pacemaker-watcher a watchdog-reboot is observed when the
pacemaker-remote-package is being updated.

Version-Release number of selected component (if applicable):
pacemaker-1.1.15 - any release till now

How reproducible:
100%

Steps to Reproduce:
1. Start pacemaker_remote on remote-node: systemctl start pacemaker_remote
2. Possibly wait till cluster has settled starting resources on remote-node
   and alike
3. yum reinstall pacemaker-remote

Actual results:
Watchdog-Reboot
empty /usr/lib/systemd/system/pacemaker_remote.service
leads to pacemaker_remote-service not able to start anymore

Expected results:
pacemaker_remote-service restarted during installation and
running as before

Additional info:
first research shows that it seems to be related with the scriptlet
in pacemaker-remote-package:
%postun remote
%systemd_postun_with_restart pacemaker_remote.service

stopping in one of the first scriptlets (%pre) executed during install
and started in one of the last (%posttrans) is working properly.

Issue is definitely not observed on cluster-nodes running pacemaker +
sbd with pacemaker-watcher.

This can be triggered when using SBD on remote nodes.  However, as of RHEL 7.3, SBD on remote nodes is *not* supported.

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-2016-2578.html