Bug 1394929

Summary:	During rolling upgrade all systemd services should be stopped before upgrade
Product:	[Red Hat Storage] Red Hat Storage Console	Reporter:	Vasu Kulkarni <vakulkar>
Component:	ceph-ansible	Assignee:	Sébastien Han <shan>
Status:	CLOSED ERRATA	QA Contact:	ceph-qe-bugs <ceph-qe-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2	CC:	adeza, aschoen, ceph-eng-bugs, gmeno, kdreyer, nthomas, sankarshan, tchandra
Target Milestone:	---
Target Release:	2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-ansible-1.0.5-44.el7scon	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-22 23:43:04 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 Vasu Kulkarni 2016-11-14 19:17:49 UTC

Description of problem:

1) During 1.3.x , upgrade testing, the manual steps involved stopping the ceph services before we upgrade, currently the rolling-upgrade.yml doesn't stop the services but does restart at the end of the upgrade, 

Even though this is working now, we might potentially hit systemd issues since systemd doesn't like files getting updated while in use.

Comment 2 Ken Dreyer (Red Hat) 2016-11-14 21:02:23 UTC

This is the approach we're taking in order to resolve the latest rolling_update bugs (like 1391675 and 1394928)

https://github.com/ceph/ceph-ansible/pull/1093

Comment 3 Andrew Schoen 2016-11-14 21:14:49 UTC

The upstream PR (https://github.com/ceph/ceph-ansible/pull/1093) has been merged and the commits pushed downstream.

Comment 8 Tejas 2016-11-15 05:41:02 UTC

Hi Vasu,

    I verified this on ceph-ansible-1.0.5-44.el7scon, and saw no issues .

Thanks,
Tejas

Comment 9 Tejas 2016-11-15 06:39:24 UTC

Movingto Verified

Comment 12 errata-xmlrpc 2016-11-22 23:43:04 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://access.redhat.com/errata/RHBA-2016:2817