Just for information.
I had the same problem and in addition to all of the above I had to edit manually the /etc/pve/corosync.conf file.
I removed the node-entry and increased the value of config_version before restarting corosync and pve-cluster.
After all of that everything worked fine.
OK, marked as solved even though I repeat that it might be interesting to check whether or not the upgrade is the culprit for messing up the hosts file.
My system really worked fine before the upgrade....
Anyway, thanks again :-)
After doing NOTHING at all, now it seems to be working again :-)
Maybe there is something to look into:
I originally started to describe the problem here:
As described there, after the update from...
Uhm, yeah this seems to be a different problem! I created a new topic for it:
Thanks for the super quick anwser!! :)
BTW: I DID update the hosts file and I could then of course ssh using...
after updating my 4 server cluster from 5.2 to 5.3 I got a severe problem.
When starting a VM I get:
TASK ERROR: start failed: command '/usr/bin/kvm -id 100 -name Xubuntu-Base -chardev 'socket,id=qmp,path=/var/run/qemu-server/100.qmp,server,nowait' -mon 'chardev=qmp,mode=control'...
I have a similar problem: TASK ERROR: Failed to run vncproxy.
BUT I also get this error when trying to start a console to a VM on the very proxmox server I am connected to. So I get the error when trying to start a console to ANY VM in my cluster.
4 server cluster...