Bug 1637965

Summary:	ceph-nfs and VIP race on service startup
Product:	Red Hat OpenStack	Reporter:	Tom Barron <tbarron>
Component:	puppet-tripleo	Assignee:	Tom Barron <tbarron>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	low	Docs Contact:
Priority:	low
Version:	13.0 (Queens)	CC:	jjoyce, jschluet, lmarsh, slinaber, tvignaud
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	puppet-tripleo-8.3.6-2.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-13 22:29:59 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 Tom Barron 2018-10-10 12:12:31 UTC

Description of problem: ceph-nfs service can start before the colocation constraint for its VIP is created


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


How reproducible: Deploy the overcloud with manila and cephfs with nfs back end

Actual results: Sometimes ceph-nfs service will fail and be restarted by pacemaker.  When restarted the VIP will be ready and the service will come up OK but 'pcs status' will show that there was a failure.  This can lead to concern on the part of cloud operators and potentially to service cases.


Expected results: No race, VIP is ready when ceph-nfs is started.

Comment 7 errata-xmlrpc 2018-11-13 22:29:59 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-2018:3587