Search results

If anyone come across this thread: The problem was 'simply' that one (and only one in a five node cluster) node wasnt seeing the new node. I've use the 'corosync-cfgtool -s' on every node to detect it and after a 'systemctl restart pve-cluster.service corosync.service' everything is working okay !

I add that I have rigorously followed the documentation at https://pve.proxmox.com/wiki/Cluster_Manager for removing an adding the node. There I read: If, for whatever reason, you want this server to join the same cluster again, you have to reinstall Proxmox VE on it from scratch...

Hello, (fully updated pve 6.4 cluster) So I decommissioned an old node "node3", I have removed it okay, the cluster is healthy. I then configured a totally new node with the same name, same ring0 IP and added it with the GUI (join cluster and copy/pasted the info from another node) but the...

OK thanks. Is there a way to do so without the need to reboot all the VMs (as we can't live migrate to a node with a downgraded qemu) ?

Thank you for the follow up. What is the recommended temporary workaround please ?

I am also affected by this. 5 nodes cluster, all fully updated to latest versions. Storage is on NFS. Only one node seems to be affected. The VMs are freezed, no VNC-able, no network, no clean shutdown capable. I was able to hard-stop (not great...) and migrate them to another node. The...