PVE 7.4-16 NoVNC Cannot Connect unless pveproxy restarted

[BeDazzler]

Hi All,

I recently upgraded a cluster of 5x PVE 7.3 nodes to 7.4-16 at the same time as performing hardware upgrades (complete server replacement).

The approach used was migrate workloads off one node at a time, delnode and remove host folder in /etc/pve/nodes, then re-join cluster as new hardware (same name).

This all worked fine, however I now have an issue where nodes in the cluster cannot migrate (shows @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!) and NoVNC is not working.

I can temporarily resolve this via systemctl restart pveproxy, however the same issue reappears on the same nodes later.

I've been reading the Proxmox manual and the recommendation is to regenerate certificates.

Will regenerating certificates upset the cluster in any way ?

Is this the right approach?

Happy to hear input from others here.

Many thanks.

 

[sterzy]

Will regenerating certificates upset the cluster in any way ?

Is this the right approach?

This should be fine and yes this is exactly what we recommend in this case [1]:

After removal of the node, its SSH fingerprint will still reside in theknown_hosts of the other nodes. If you receive an SSH error after rejoining a node with the same IP or hostname, run pvecm updatecerts once on the re-added node to update its fingerprint cluster wide.

So just run pvecm updatecerts.

[1]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node

 

[BeDazzler]

This should be fine and yes this is exactly what we recommend in this case [1]:

So just run pvecm updatecerts.

[1]: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node

Thank you Stefan, much appreciated. I will update the certs on all cluster nodes.