Comment 7 for bug 1771523

We need actual functional testing of the AggregateMultiTenancyIsolation filter - because it's confusing in how it works. It looks like the problem with that filter is hosts in the tenant-isolated aggregates are restricted to those tenants, but the tenants themselves are not restricted to hosts in that tenant-isolated aggregate. So if the scheduler picks a few hosts where some are in and some are outside the aggregate and weighs the hosts outside the aggregate higher, the tenant will get those hosts rather than the isolated hosts.