This message was deleted.

Hi @quaint-alarm-7893, could you create a support bundle for us to check the current status of your cluster?

generating it now, sorry, it takes FOREVER! 🙂

Thanks! I will check it

so fyi, ultimately the server came back online. we're talking like 4hrs later it came back into the cluster... 🤷‍♂️ the big issue i had was by the node being offline, all volumes that were primary to that node, were not accessable, and the replicas disappeared from longhorn, which is a huge risk.

Hi @quaint-alarm-7893, sorry I did not really understand your situation. Did you mean the node somehow comes back but some replicas are disappeared?

@salmon-city-57654 yes. basically the node was rebooted. when it came back up, it got stuck in a etcd error and wouldnt come online (it showed in harvester that the kubelet was nto running and the rke2-server service was not running on the node). at that point, one of the vms i had, the volumes that were attached to that node, but had replicas on other nodes had an odd issue where the replicas were dropped, and there was only one replica. because it was on the node that was offline, i couldnt get the vm up.