I noticed that they'd both ended up on the same hypervisor today (cloudvirt1021). I moved tools-k8s-haproxy02 to cloudvirt1017 to correct the issue, but letting the scheduler figure that out by placing them both in an anti-affinity group would be better than adding them to the spread alert, I think, (though we could do that too).
|Open||None||T262350 bad failure cases for wmcs custom puppet enc|
|Open||None||T267082 Rebuild Toolforge servers that should not have NFS mounted (and with affinity)|
|Resolved||taavi||T252239 Rebuild tools-k8s-haproxy-* as an anti-affinity server group|