[Openstack-operators] Problems with AggregateMultiTenancyIsolation while migrating an instance

Massimo Sgaravatto massimo.sgaravatto at gmail.com
Wed May 30 10:21:32 UTC 2018

The problem is indeed with the tenant_id

When I create a VM, tenant_id is ee1865a76440481cbcff08544c7d580a
(SgaraPrj1), as expected

But when, as admin, I run the "nova migrate" command to migrate the very
same instance, the tenant_id is 56c3f5c047e74a78a71438c4412e6e13 (admin) !

Cheers, Massimo

On Wed, May 30, 2018 at 1:01 AM, Matt Riedemann <mriedemos at gmail.com> wrote:

> On 5/29/2018 3:07 PM, Massimo Sgaravatto wrote:
>> The VM that I am trying to migrate was created when the Cloud was already
>> running Ocata
> OK, I'd added the tenant_id variable in scope to the log message here:
> https://github.com/openstack/nova/blob/stable/ocata/nova/sch
> eduler/filters/aggregate_multitenancy_isolation.py#L50
> And make sure when it fails, it matches what you'd expect. If it's None or
> '' or something weird then we have a bug.
> --
> Thanks,
> Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20180530/92559942/attachment.html>

More information about the OpenStack-operators mailing list