This message was deleted.
# general
a
This message was deleted.
h
@gifted-helicopter-8095 From what I can see here, the error indicates that rancher is still trying to connect to the old node sih001 even after you tried to delete it. This could be due to a stuck finalizer or a state not updated in etcd.
You can try and forcibly remove the node from the cluster. You can do it from the rancher UI or using kubectl.
kubectl get nodes to get the nodes and kubectl delete node name_of_node, to delete the node.
524 Views