AggregateMultiTenancyIsolation description inaccuracy

[Roman Kolodziejczyk]

The issue in bug #1328400 (https://bugs.launchpad.net/bugs/1328400) appears to be affecting the newest Openstack documentation. The changes made in the repository (https://review.opendev.org/c/openstack/openstack-manuals/+/281620) do not seem to have made it to the web version, or were lost at some point.

Currently the site still says that Tenants in an aggregate with this enabled will not have other Tenants deploying into that aggregate when that is not the case. Other Tenants are still allowed to deploy into hosts on the Aggregate on both Yoga and Ussuri in my testing.

Ideally the changed text from the patch above just needs to be re-added since it is more clear about the actual behavior.

[Andreas Jaeger (jaegerandi)]

Which page exactly shows the wrong information?

[Roman Kolodziejczyk (romankolodz)]

https://docs.openstack.org/nova/xena/admin/scheduling.html#aggregatemultitenancyisolation
through to;
https://docs.openstack.org/nova/latest/admin/scheduling.html#aggregatemultitenancyisolation

These all have the incorrect note that a Tenant outside of the aggregate will be denied use of the Tenant isolated aggregate. This has not been the behavior in testing.