HI Frédéric, > I think this message shows up as this very specific post adoption 'osd' service has already been marked as 'deleted'. Maybe when you ran the command for the first time. > The only reason it still shows up on 'ceph orch ls' is that 95 OSDs are still referencing this service in their configuration. > > Once you'll have edited all OSDs /var/lib/ceph/$(ceph fsid)/osd.xxx/unit.meta files (changed their service_name) and restarted all OSDs (or recreated these 95 OSDs encrypted under another service_name), the 'osd' service will disappear by itself and won't show up anymore on 'ceph orch ls' output. At least this is what I've observed in the past. Yes, as Eugen pointed out, it doesn’t make sense to try to delete an unmanaged service using the orchestrator. >> My hunch is that some persistent state is corrupted, or there’s something else >> preventing the orchestrator from successfully refreshing its device status, but >> I don’t know how to troubleshoot this. Any ideas? > > I don't think this is related to the 'osd' service. As suggested by Tobi, enabling cephadm debug will tell you more. Agreed. I’ll dig through the logs some more today to see if I can spot any problems. Cheers, /rjg _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |