Bug 1656460

Summary: define tooling/strategy to upgrade ceph-disk osds when ceph-disk is no longer there
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, tchandra, tserlin
Target Milestone: rc   
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-14.2.0 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:    
Bug Blocks: 1656454, 1656468, 1656494, 1656506, 1770266, 1770317    

Description Andrew Schoen 2018-12-05 15:05:56 UTC
When a user updates to 4.x ceph-disk will no longer be there. We need a mechanism to easily port all the existing OSDs from ceph-disk to ceph-volume.

Comment 6 Andrew Schoen 2018-12-05 15:30:05 UTC
I suspect this will be a new ceph-volume subcommand that will mass upgrade all existing ceph-disk OSDs to ceph-volume. The simple subcommand does this one OSD at a time, but that's not a manageable process on a large cluster.

Comment 7 Andrew Schoen 2019-06-11 21:11:06 UTC
This was completed and merged upstream to nautilus. The process is to run ``ceph-volume simple scan`` and then ``ceph-volume simple activate --all``.

Comment 11 Vasishta 2020-01-17 06:12:50 UTC
We have tried  ``ceph-volume simple scan`` and then ``ceph-volume simple activate --all`` using ceph-ansible
Bug 1656506 (containerized scenario) , Bug 1656468 (ceph-ansible BZ addressing for baremetal scenario) has been moved to verified state.

Thus moving this BZ to VERIFIED state.

Regards,
Vasishta Shastry
QE, Ceph

Comment 13 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