Bug 1356687
| Summary: | ceph-ansible needs a way to manage an existing cluster not created by ceph-ansible | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Storage Console | Reporter: | Andrew Schoen <aschoen> |
| Component: | ceph-ansible | Assignee: | Andrew Schoen <aschoen> |
| Status: | CLOSED ERRATA | QA Contact: | Rachana Patel <racpatel> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2 | CC: | adeza, aschoen, ceph-eng-bugs, ceph-qe-bugs, hnallurv, kdreyer, kurs, nthomas, sankarshan |
| Target Milestone: | --- | Flags: | kurs:
needinfo-
|
| Target Release: | 2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-1.0.5-27.el7scon | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-23 19:56:50 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: | |||
|
Description
Andrew Schoen
2016-07-14 17:39:21 UTC
The rationale here is that we need ceph-ansible to be able to operate a cluster that was not created initially by ceph-ansible. The upstream playbook take-over-existing-cluster.yml provides this functionality. Andrew, you're working on documentation for this feature, right? (In reply to Ken Dreyer (Red Hat) from comment #5) > Andrew, you're working on documentation for this feature, right? I sent a note to ceph-qe-list with usage instructions: http://post-office.corp.redhat.com/archives/ceph-qe-list/2016-July/msg00052.html version - ceph-ansible-1.0.5-27.el7scon had a bug working with ceph-ansible-1.0.5-31.el7scon. Hence moving to verified 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-2016:1754 |