Yes ! That was is, upon closer inspection, one of the private IP's in /etc/hosts was wrong.
I now have quorum back after running
systemctl restart corosync && systemctl start pve-ha-lrm && systemctl start pve-ha-crm
Thank you very much for the help, I'll continue with the upgrade path :)
Thank you, so I did reboot one of the host (PVE3) and re-executed the pve5to6 script, here's the output, I edited the public IP which was shown on IT (REDACTED_PUB_IP instead)
root@pve3:~# pve5to6
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =
Checking for package updates..
PASS: all...
Hello Mira and thank you for the reply !
Yes I did run pve5to6 before starting and the only error on both nodes was that Corosync was at v2 which was expected (and hence the v3 upgrade)
To clarify : I did not completed the Proxmox v6 upgrade (yet), I just updated to Corosync v3 and stopped...
Hello Proxmox community ! :)
I inherited a Proxmox 2-nodes setup at my new workplace and since it's running the EOL 5.4.15, I thought I would take a look at how to upgrade it to 6.x which is supported.
So I started the procedure here https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0 and...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.