Hi!
Yes, currently, this is the expected behavior as the HA Manager will detect that each HA resource is on the same node as a HA resource it must not be together with and schedules both to move to other nodes.
Negative HA resource affinity...
Hi,
I was able to observe the same issue when trying with Chromium. Patch sent: https://lore.proxmox.com/pve-devel/20260407102518.57975-1-f.ebner@proxmox.com/T/
Hi!
There should be no specific reason why the fencing status is either on the top or the bottom. I couldn't yet reproduce the order of the first screenshot, does it happen randomly on reloading or move while staying on the page where it...
We recently uploaded the 7.0 (rc6) kernel to our repositories. The current default kernel for the Proxmox VE 9 series is still 6.17, but 7.0 is now an option.
We plan to use the 7.0 kernel as the new default for the upcoming Proxmox VE 9.2 and...
Great that the details helped you!
The recommended way to put an LRM service into an idle state would be to either move all of the HA resources placed on that node to another node or put all the HA resources placed on that node into the...
After all the HA resources were set to 'ignored', it takes roughly 10 minutes for the LRM and 15 minutes for the CRM to release their watchdogs and become idle. Maybe the network interruption for both the production and test setup were done while...
Hi!
Thanks for the report! I suppose there is a HA node affinity rule which makes the HA resource failback to the old node. As the node fails, the HA Manager will move the HA resource but not clean up the cloudinit image from the failed node as...
Hm, then it could be a kernel panic inside the VM that is causing it and isn't written to the disk anymore if it doesn't show up in the syslog, e.g. journalctl -b -1... Maybe you can setup netconsole [0] [1] or some other log-persisting setup to...