Description of problem: ceph-volume is not capable of activating containerized OSDs. Version-Release number of selected component (if applicable): How reproducible: [root@ceph-osd0 ~]# ceph-volume simple activate 1 04271cdf-a533-4bfb-b310-492c936f3e7a --no-systemd usage: ceph-volume simple activate [-h] [--file FILE] [ID] [FSID] ceph-volume simple activate: error: unrecognized arguments: --no-systemd Actual results: OSDs won’t start after an upgrade The --no-systemd flag does not exist Expected results: ceph-volume must manage ceph-disk’s OSDs and restart them after an upgrade to 4.0 The --no-systemd exists Additional info: This is a must-have for the ceph-disk to ceph-volume transition.
Not a blocker for 3.2.
I don't understand how this is suddenly an issue for 3.2 if the feature request was initially targeted for 4.0. I don't think there is any Release Note needed here. @Sebastien do you think this warrants a release note? Mind clarifying if you really need this for 3.2?
@Alfredo, I changed the flag so the engine will stop retargetting this for 3.*
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/RHSA-2019:2538