Hi Tim, is this still an issue? If it is, I recommend to add some more details so it's easier to follow your train of thought. ceph osd tree ceph -s ceph health detail ceph orch host ls And then please point out which host you're trying to get rid of. I would deal with the rgw thing later. Is it possible, that the phantom host actually had OSDs on it? Maybe that needs to be cleaned up first. I had something similar on a customer cluster recently where we hunted failing OSDs but it turned out they were removed quite a while ago, just not properly cleaned up yet on the filesystem. Thanks, Eugen Zitat von Tim Holloway <timholloway34@gmail.com>:
It's getting worse.
As many may be aware, the venerable CentOS 7 OS is hitting end-of-life in a matter of days.
The easiest way to upgrade my serves has been to simply create an alternate disk with the new OS, turn my provisioning system loose on it, yank the old OS system disk and jack in the new one.
However, Ceph is another matter. For that part, the simplest thing to do is to destroy the Ceph node(s) on the affected box, do the OS upgrade, then re-create the nodes.
But now I have even MORE strays. The OSD on my box lives on in Ceph in the dashboard host view even though the documented removal procedures were followed and the VM itself was destroyed.
Further, this last node is an RGW node and I cannot remove it from the RGW configuration. It not only shows on the dashboard, it also lists as still active on the command line and as entries in the config database no matter what I do.
I really need some solution to this, as it's a major chokepoint in the upgrade process
Tim _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io