Oh right, in that case you'll have to clean up manually. On the
affected host run
cephadm ls --no-detail | grep osd
This should show you the remainders of the faulty OSDs. Then run
cephadm rm-daemon --name osd.0 --force --fsid {YOUR_CLUSTER_FSID}
cephadm rm-daemon --name osd.3 --force --fsid {YOUR_CLUSTER_FSID}
Check with 'podman|docker ps' if there are dead pods running and kill
them, just to be sure.
Wait a bit, the orchestrator should clean up 'ceph orch ps' output.
Then you can zap the drives either with:
ceph orch device zap <host> /dev/sdX --force
or locally on the host with:
cephadm ceph-volume lvm zap --destroy /dev/sdX
Then set your OSD spec to managed and the orchestrator will redeploy OSDs.
Zitat von lejeczek <peljasz@xxxxxxxxxxx>:
at this point - after having followed that Redhat's doc - as I
showed with 'tree' results, with the 'orch' bits I get:
-> $ ceph orch osd rm 0 3 --force --zap
Unable to find OSDs: ['0', '3']
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
