Bug 1656908

Summary: [ceph-ansible] Ceph nfs installation fails at task start nfs gateway service in ubuntu ipv6 deployment
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: subhash <vpoliset>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: medium Docs Contact: Bara Ancincova <bancinco>
Priority: medium    
Version: 3.2CC: aschoen, ceph-eng-bugs, gabrioux, gmeno, hnallurv, jbrier, nthomas, pasik, rraja, sankarshan, seb, tchandra, tserlin
Target Milestone: rc   
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.2.17-1.el7cp Ubuntu: ceph-ansible_3.2.17-2redhat1 Doc Type: Bug Fix
Doc Text:
.Deploying NFS Ganesha gateway on Ubuntu IPv6 systems works as expected When deploying NFS Ganesha gateway on Ubuntu IPv6 systems, the `ceph-ansible` utility failed to start the `nfs-ganesha` service. As a consequence, the installation process failed as well. This bug has been fixed, and the installation process proceeds as expected.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-21 15:10:24 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:
Bug Depends On: 1660063    
Bug Blocks: 1629656, 1726135    

Comment 5 Ram Raja 2018-12-26 11:25:27 UTC 
The first playbook 'site.yml' run fails when nfs-ganesha cannot be enabled due to
https://bugzilla.redhat.com/show_bug.cgi?id=1660063

Rerunning the playbook 'site.yml' to install only deploy nfs-ganesha server succeeds (i.e
no ansible failure reported, and nfs-ganesha server is started), but the nfs-ganesha service
still is not enabled due to the BZ 1660063.
Comment 12 Giridhar Ramaraju 2019-08-05 13:11:05 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 13 Giridhar Ramaraju 2019-08-05 13:12:06 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 15 errata-xmlrpc 2019-08-21 15:10:24 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/RHSA-2019:2538