Bug 1651792 - ceph-nfs and VIP race on service startup
Summary: ceph-nfs and VIP race on service startup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 14.0 (Rocky)
Assignee: Tom Barron
QA Contact: Yogev Rabl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-20 20:53 UTC by Giulio Fidente
Modified: 2019-01-11 11:54 UTC (History)
11 users (show)

Fixed In Version: puppet-tripleo-9.3.1-0.20181010034751.157eaab.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:54:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 608446 0 None None None 2018-11-20 20:53:58 UTC
OpenStack gerrit 611203 0 None None None 2018-11-20 20:55:02 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:54:58 UTC

Description Giulio Fidente 2018-11-20 20:53:59 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 25 Yogev Rabl 2018-12-04 14:43:51 UTC 
verified with Ceph 3.2
Comment 27 errata-xmlrpc 2019-01-11 11:54:47 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/RHEA-2019:0045
Note You need to log in before you can comment on or make changes to this bug.