dakralex's latest activity
-
dakralex replied to the thread HA affinity problem (?).I'm sorry, but I cannot reproduce this issue with the information you gave me. There's one newer version of pve-ha-manager on trixie/pve-test (5.1.0), but the bug fix in that version shouldn't be related to this here. Can you share the... -
dakralex replied to the thread HA affinity problem (?).On another note, what pve-ha-manager version is running on the nodes?
-
dakralex replied to the thread HA affinity problem (?).If the HA status report from above is the exact same as it was before setting pve1 in maintenance mode (the HA status report's timestamp is later than the syslog), then I cannot reproduce it with this configuration either. Are you sure that the...
-
dakralex replied to the thread HA affinity problem (?).Thanks! If it's possible, it would be great to have a more complete reproducer for this to investigate the issue. The names can be changed, the only important part is that the changed names have the same alphabetical ordering (e.g. SN140 ->...
-
dakralex replied to the thread HA affinity problem (?).Hi! I have recreated your exact setup as described by the status output and rules config above and couldn't reproduce this either. What should happen is that as soon as pve1 is put in maintenance mode, the vm:102 will select a new node (it will...
-
dakralex replied to the thread HA groups fails to migrate after upgrade 8 to 9.See my reply above, the syslog on the current HA Manager (master) node should show a regular error that the HA groups couldn't be migrated and the reason why. This should point you in the direction what is missing (e.g. maintenance mode, not...
-
dakralex replied to the thread How to fail a looping HA VM migration?.Hi! The versions of the node seem a bit out of date, pve-manager 9.0.5 is from mid-August. Could you try upgrading the nodes to see if this is fixed in a more current version? The HA groups should have been migrated with the upgrade from PVE 8...
-
dakralex replied to the thread [SOLVED] kernel: landlock - Error on VM boot - assistance required.Was there any console output for the qmstart task for the VM 410? Is there anything shown at boot on the machine? Is the boot disk (scsi0) still intact (e.g., no fs corruption, system files are readable)? Else I could not see anything off from...