Bug 1301629
Summary: | Deployment of Ceph times out in IPv6 | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Giulio Fidente <gfidente> |
Component: | openstack-puppet-modules | Assignee: | Giulio Fidente <gfidente> |
Status: | CLOSED ERRATA | QA Contact: | Marius Cornea <mcornea> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 (Kilo) | CC: | apevec, dnavale, emacchi, gfidente, lbezdick, lhh, mburns, ohochman, rhel-osp-director-maint, srevivo, yeylon |
Target Milestone: | z4 | Keywords: | ZStream |
Target Release: | 7.0 (Kilo) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-puppet-modules-2015.1.8-46.el7ost.noarch | Doc Type: | Bug Fix |
Doc Text: |
Previously, Ceph was inappropriately configured when using IPv6. As a result, the setup of Ceph in the overcloud failed, causing the deployment to timeout, if the storage network used IPv6 addresses.
With this update, the relevant Ceph configuration option, 'ms_bind_ipv6', based on the 'CephIPv6' parameter is now used. As a result, Ceph is functional and the overcloud deployment is completed when using IPv6 for the storage network if the appropriate input parameters are provided to the Orchestration service.
|
Story Points: | --- |
Clone Of: | 1299613 | Environment: | |
Last Closed: | 2016-02-18 16:44:54 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: | |||
Bug Blocks: | 1302593, 1309822 |
Description
Giulio Fidente
2016-01-25 14:44:10 UTC
*** Bug 1301627 has been marked as a duplicate of this bug. *** [root@overcloud-controller-0 ~]# rpm -qa | grep puppet-modules openstack-puppet-modules-2015.1.8-51.el7ost.noarch [root@overcloud-controller-0 ~]# grep ms_bind /etc/ceph/ceph.conf ms_bind_ipv6 = True 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://rhn.redhat.com/errata/RHBA-2016-0265.html |