I've got a situation right now where one VM, upon reboot, encountered filesystem corruption.
Upon closer examination, I see that the Proxmox GUI doesn't accurately reflect which cluster node that VM is running on.
The GUI shows VM #107 running on node #2, whereas the KVM process with -id 107 is actually running on node #4, and is not present on node #2.
clustat(8) correctly indicates that the VM is running on node #4.
What could cause the GUI to get out of sync, how do I fix it, and where would I look (i.e. what log file) for indications of what went wrong?
-Adam
Upon closer examination, I see that the Proxmox GUI doesn't accurately reflect which cluster node that VM is running on.
The GUI shows VM #107 running on node #2, whereas the KVM process with -id 107 is actually running on node #4, and is not present on node #2.
clustat(8) correctly indicates that the VM is running on node #4.
What could cause the GUI to get out of sync, how do I fix it, and where would I look (i.e. what log file) for indications of what went wrong?
-Adam