Comment 5 for bug 1328400

HI jesse, I did a test on my new devstack, proved what my concern is right.

* I have two tenants, admin and demo
* I created an aggregate with the only one host, with the 'filter_tenant_id' = demo;
* I created a VM using admin credentials, the VM creation failed because of 'no valid host', below is the log:

2014-06-12 11:48:51.481 DEBUG nova.scheduler.filters.aggregate_multitenancy_isolation [req-ee6a294f-4da7-4456-be75-40b3701566e4 admin admin] Enter AggregateMultiTenancyIsolation metadata {u'filter_tenant_id': set([u'9dac3fc8aaae4f7b80e7c8155a512f0a'])},tenantid cf2d81356beb4c8390aadeb3432f6b3f host_passes /opt/stack/nova/nova/scheduler/filters/aggregate_multitenancy_isolation.py:46
2014-06-12 11:48:51.482 DEBUG nova.scheduler.filters.aggregate_multitenancy_isolation [req-ee6a294f-4da7-4456-be75-40b3701566e4 admin admin] (devstack, devstack) ram:6962 disk:27648 io_ops:0 instances:1 fails tenant id on aggregate host_passes /opt/stack/nova/nova/scheduler/filters/aggregate_multitenancy_isolation.py:49