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.
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