Hi everyone,I've recently updated the secondary link (ring1_addr) for my Proxmox VE 9.0.10 cluster network and adjusted the configuration on all nodes accordingly. The cluster communication is working perfectly, and everything seems fine operationally. I've verified this with the following checks:
Has anyone encountered this issue before? Is this a known bug in Proxmox VE 9.0.10, or is there a specific step I might have missed to refresh the Web-UI display?
Any suggestions on how to resolve this or force the UI to update the displayed IPs would be greatly appreciated!
Thanks in advance for your help!
*SOLVED* Somehow it's show correctly after rebooting the nodes again(?).
- pvecm status shows the correct status and communication.
- corosync-cfgtool -s confirms the updated IPs for the secondary link.
- The corosync.conf file correctly reflects the new ring1_addr IPs.
- All nodes have been rebooted to ensure changes take effect.
Has anyone encountered this issue before? Is this a known bug in Proxmox VE 9.0.10, or is there a specific step I might have missed to refresh the Web-UI display?
Any suggestions on how to resolve this or force the UI to update the displayed IPs would be greatly appreciated!
Thanks in advance for your help!
*SOLVED* Somehow it's show correctly after rebooting the nodes again(?).
Last edited: