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

Massimo Sgaravatto massimo.sgaravatto at gmail.com
Tue May 29 20:07:39 UTC 2018


The VM that I am trying to migrate was created when the Cloud was already
running Ocata

Cheers, Massimo

On Tue, May 29, 2018 at 9:47 PM, Matt Riedemann <mriedemos at gmail.com> wrote:

> On 5/29/2018 12:44 PM, Jay Pipes wrote:
>
>> Either that, or the wrong project_id is being used when attempting to
>> migrate? Maybe the admin project_id is being used instead of the original
>> project_id who launched the instance?
>>
>
> Could be, but we should be pulling the request spec from the database
> which was created when the instance was created. There is some shim code
> from Newton which will create an essentially fake request spec on-demand
> when doing a move operation if the instance was created before newton,
> which could go back to that bug I was referring to.
>
> Massimo - can you clarify if this is a new server created in your Ocata
> test environment that you're trying to move? Or is this a server created
> before Ocata?
>
> --
>
> Thanks,
>
> Matt
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20180529/1195a676/attachment.html>


More information about the OpenStack-operators mailing list