Bug 1372009

Summary:	pacemaker-remote rpm does not properly restart pacemaker_remote during package upgrade, potentially triggering a watchdog fence
Product:	Red Hat Enterprise Linux 7	Reporter:	Klaus Wenninger <kwenning>
Component:	pacemaker	Assignee:	Klaus Wenninger <kwenning>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.3	CC:	abeekhof, cfeist, cluster-maint, djansa, kgaillot, lmiksik, tlavigne
Target Milestone:	rc
Target Release:	7.3
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	pacemaker-1.1.15-11.el7	Doc Type:	No Doc Update
Doc Text:	The issue was not present in any released version.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-03 19:00:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Klaus Wenninger 2016-08-31 17:05:55 UTC

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.

Comment 3 Chris Feist 2016-09-26 19:57:57 UTC

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

Comment 5 errata-xmlrpc 2016-11-03 19:00:22 UTC

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