On Fri Sep 19, 2025 at 4:08 PM CEST, Daniel Kral wrote: > Some last-minute changes to the positive resource affinity's heuristic > (which is described in the next paragraph) in the initial implementation > broke the mixed usage of resource affinity rules. > > Strict positive resource affinity rules narrow down the possible nodes > to a single candidate for a HA resource A, which is the node, where the > most of the HA resources in the positive affinity rule are already > running on and in case of a tie the alphabetically first node is chosen. > > If the chosen node contains a HA resource B, which is in negative > affinity with the HA resource A, then there will be no possible node > left as it is removed now as well and won't resolve the incorrect node > placement (see the test cases for more details).
For completeness, these patches are already applied: 6db0df7c test: add additional mixed resource affinity rule test cases 9ff6a5e1 manager: fix precedence in mixed resource affinity rules usage adae0e3e tests: add regression tests for mixed resource affinity rules _______________________________________________ pve-devel mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
