| Summary: | Ceph issues on OSP10 integrated with an existing older Ceph Cluster | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Kiran Thyagaraja <kiran> |
| Component: | ceph | Assignee: | John Fulton <johfulto> |
| Status: | CLOSED DUPLICATE | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 10.0 (Newton) | CC: | jdurgin, johfulto, jomurphy, lhh, nlevine, srevivo |
| Target Milestone: | --- | ||
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-11-16 12:36: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: | |
|
Description
Kiran Thyagaraja
2016-11-15 16:45:35 UTC
Hi Kiran, In order to make the Ceph2 clients shipped in the OSP10 images work with a Ceph1.3 server, you need to enable a flag in OSPd for backwards compatibility. To do this, please add some additional Heat to your template as described in: https://bugzilla.redhat.com/show_bug.cgi?id=1393581#c8 As linked in the BZ above, OSP10 documentation should be updated in time to include the above step. Also, relevant to OSP10 Ceph clients and external Ceph servers is the following: https://bugzilla.redhat.com/show_bug.cgi?id=1394587#c21 The above isn't a doc issue of including the flag, but of a change that will come to OSP10. You can test as if the fix had shipped by using the following for your ceph-external.yaml in /usr/share/openstack-tripleo-heat-templates/puppet/services https://review.openstack.org/#/c/397819/1/puppet/services/ceph-external.yaml Please let me know how that works. Update: The ceph backward compatibility solution works. So, this (not a)bug may be closed. Many thanks. Kiran, thanks for the update. Since it was the same root cause and fix of BZ 1393581 I am going to mark this as a duplicate. *** This bug has been marked as a duplicate of bug 1393581 *** |