I see this in the web interface in Hosts and under cn03’s devices tab SAMSUNG_HD502HI_S1VFJ9ASB08190 Unknown n/a sdg mon.cn04 1 total Which doesn’t make sense. There is no daemons running on this host and I noticed the daemon lists looks like its one that should be on another node. There is already a mon.cn04 running on the cn04 node. -jeremy
On Saturday, Jun 10, 2023 at 11:10 PM, Me <jeremy@skidrow.la (mailto:jeremy@skidrow.la)> wrote: I also see this error in the logs:
6/10/23 11:09:01 PM[ERR]host cn03.ceph does not exist Traceback (most recent call last): File "/usr/share/ceph/mgr/orchestrator/_interface.py", line 125, in wrapper return OrchResult(f(*args, **kwargs)) File "/usr/share/ceph/mgr/cephadm/module.py", line 1625, in remove_host self.inventory.rm_host(host) File "/usr/share/ceph/mgr/cephadm/inventory.py", line 108, in rm_host self.assert_host(host) File "/usr/share/ceph/mgr/cephadm/inventory.py", line 93, in assert_host raise OrchestratorError('host %s does not exist' % host) orchestrator._interface.OrchestratorError: host cn03.ceph does not exist
On Saturday, Jun 10, 2023 at 10:41 PM, Me <jeremy@skidrow.la (mailto:jeremy@skidrow.la)> wrote: I’m going through the process of transitioning to new hardware. Pacific 16.2.11.
I drained the host, all daemons were removed. Did the ceph orch host rm <hostname>
[ceph: root@cn01 /]# ceph orch host rm cn03.ceph Error EINVAL: host cn03.ceph does not exist
Yet I see it here:
ceph osd crush tree |grep cn03 -10 0 host cn03
Web interface says:
ceph health HEALTH_WARN 1 stray host(s) with 1 daemon(s) not managed by cephadm
ceph orch host rm cn03.ceph --force Error EINVAL: host cn03.ceph does not exist
No daemons are running. Something has a bad state.
What can I do to clear this up? The previous host went without a problem and when all services were drained and I did the remove, it just completely disappeared as expected.
Thanks -jeremy