Bug 1372009 – pacemaker-remote rpm does not properly restart pacemaker_remote during package upgrade, potentially triggering a watchdog fence

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1372009 - pacemaker-remote rpm does not properly restart pacemaker_remote during package upgrade, potentially triggering a watchdog fence

Summary:	pacemaker-remote rpm does not properly restart pacemaker_remote during packag...

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	pacemaker (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	Unspecified Linux

Priority	urgent Severity urgent
Target Milestone:	rc
Target Release:	7.3
Assigned To:	Klaus Wenninger
QA Contact:	cluster-qe@redhat.com
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2016-08-31 13:05 EDT by Klaus Wenninger
Modified:	2016-11-03 15:00 EDT (History)
CC List:	7 users (show)

See Also:
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 15:00:22 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2016:2578	normal	SHIPPED_LIVE	Moderate: pacemaker security, bug fix, and enhancement update	2016-11-03 08:07:24 EDT

Groups: None (edit)

Description Klaus Wenninger 2016-08-31 13:05:55 EDT

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 15:57:57 EDT

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 15:00:22 EDT

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

Note You need to log in before you can comment on or make changes to this bug.