Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1656454

Summary: [tracker] ceph-disk to ceph-volume transition in 4.x
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Andrew Schoen <aschoen>
Component: Ceph-VolumeAssignee: Christina Meno <gmeno>
Status: CLOSED ERRATA QA Contact: Vasishta <vashastr>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: ceph-eng-bugs, ceph-qe-bugs, gmeno, kdreyer, pasik, tchandra, tserlin, vashastr
Target Milestone: rcKeywords: Tracking
Target Release: 4.0   
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: 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: 1640273, 1655168, 1656460, 1656468, 1656494, 1656506    
Bug Blocks:    

Description Andrew Schoen 2018-12-05 14:52:07 UTC 
This BZ will be used to collect all BZs related to the transition from ceph-disk to ceph-volume in RHCS 4.x
Comment 11 Alfredo Deza 2019-10-04 13:03:37 UTC 
All the tickets referenced here are either CLOSED, ON_QA, or MODIFIED. So I am going to change the state to ON_QA to better reflect the overall state (not NEW)
Comment 13 Vasishta 2020-01-17 07:44:13 UTC 
Since all the dependent BZs of this tracker has been VERIFIED or CLOSED, moving to VERIFIED state.

Regards,
Vasishta Shastry
QE, Ceph
Comment 16 errata-xmlrpc 2020-01-31 12:45:18 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/RHBA-2020:0312