Bug 1656468
| Summary: | ceph-ansible: call ceph-volume command during 4.x upgrade to port ceph-disk osds to ceph-volume | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Andrew Schoen <aschoen> |
| Component: | Ceph-Ansible | Assignee: | Ameena Suhani S H <amsyedha> |
| Status: | CLOSED ERRATA | QA Contact: | Ameena Suhani S H <amsyedha> |
| Severity: | high | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | high | ||
| Version: | 4.0 | CC: | agunn, amsyedha, anharris, aschoen, ceph-eng-bugs, ceph-qe-bugs, edonnell, gabrioux, gmeno, nthomas, shan, tserlin, vashastr |
| Target Milestone: | rc | ||
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-ansible-4.0.0-0.1.rc7.el8cp | Doc Type: | Enhancement |
| Doc Text: |
.Ceph OSDs created with `ceph-disk` are migrated to `ceph-volume` during upgrade
When upgrading to {product} 4, all running Ceph OSDs previously created by the `ceph-disk` utility will be migrated to the `ceph-volume` utility because `ceph-disk` has been deprecated in this release.
For bare-metal and container deployments of {product}, the `ceph-volume` utility does a simple scan and takes over the existing Ceph OSDs deployed by the `ceph-disk` utility. Also, do not use these migrated devices in configurations for subsequent deployments. Note that you cannot create any new Ceph OSDs during the upgrade process.
After the upgrade, all Ceph OSDs created by `ceph-disk` will start and operate like any Ceph OSDs created by `ceph-volume`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-31 12:45:18 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: | 1656460, 1790212 | ||
| Bug Blocks: | 1656454, 1730176, 1770263 | ||
|
Description
Andrew Schoen
2018-12-05 15:16:24 UTC
*** Bug 1652837 has been marked as a duplicate of this bug. *** Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri 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-2020:0312 |