Check if there are still leftover files in /etc/pve/nodes/<deleted-node>.
As long as there are files still in there, the node will show up in the UI.
Please make a backup of the files before you delete them, just to be safe!
I just went through some self inflicted pain when I added a node to my cluster when one of my other nodes was offline. I didn't know that would cause so many problems. A warning in the UI would have been nice. The offline node when brought back online just didn't want to behave correctly. It hung in the shell about 30 seconds after boot and never attached to the cluster again. I could only SSH to it. I couldn't find a solution to fix its membership in the cluster. At this point it appeared best to remove it from the cluster. This was all on 8.2.x
From a good cluster node:
Code:
pvecm nodes
pvecm delnode<nodename>
The node will still show as a ghost in the Datacenter view until the node is deleted from at least one nodes /etc/pve/nodes dir.
As long as there are files still in there, the node will show up in the UI.
Code:
rm -r /etc/pve/nodes/<nodename>
On removed node to make it standalone and files editable:
Code:
systemctl stop pve-cluster
/usr/bin/pmxcfs -l
rm -f /etc/pve/corosync.conf
rm -f /etc/corosync/corosync.conf
rm -f /etc/corosync/authkey
cd /etc/pve/nodes
rm -r <othernodename> #for all other nodes
reboot now
Node is now standalone. The node can now be re-added to a cluster if desired.
and then edit /etc/pve/ceph.conf and remove any reference to the IP of the 'unknown' node from /etc/pve/ceph.conf and then it worked flawlessly. Was able to remove 'unknown' node and then re-add without issue. This wasn't exactly what I was looking for, but directed me to what solved my problem. Thank you.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
