[nova] Improvements in migration tracking via API

Radosław Piliszek radoslaw.piliszek at gmail.com
Tue Jul 27 15:58:46 UTC 2021


Thanks, Melanie, for checking. I must have mixed up UUIDs when testing
and did not notice.
Sorry for the trouble!

-yoctozepto

On Tue, Jul 27, 2021 at 5:37 PM melanie witt <melwittt at gmail.com> wrote:
>
> On Tue, 27 Jul 2021, 08:53 +0200, Radosław Piliszek
> <radoslaw.piliszek at gmail.com> wrote:
> > On Mon, Jul 26, 2021 at 10:36 PM melanie witt <melwittt at gmail.com> wrote:
>
> [snip]
>
> >> Note that you would also have to change the API to allow showing a
> >> migration that is not of migration_type "live-migration". Currently it
> >> only allows showing an in-progress live migration.
> >
> > Ah, I see the description. But I am pretty sure I got it to retrieve
> > an arbitrary ID migration though. But the relevant listing was
> > filtered for sure. Could you confirm that?
> > Should we treat that as a bug then? I hope not because I wanted to
> > rely on it. :-)
>
> AFAICT that doesn't look possible. When I tried it in devstack I got the
> following result:
>
> $ openstack server migration show testVM 5 --os-compute-api-version 2.24
> Migration 5 for server f1aece4e-e7f7-436b-9faf-799129503dcc is not
> live-migration. (HTTP 404) (Request-ID:
> req-84e97eaf-d3b5-4287-8a52-b5193b038447)
> stack at ubuntu-controller:~$
>
> And this is the code that blocks other migration types when showing a
> server migration by ID:
>
> https://github.com/openstack/nova/blob/eaca6b7e664b1980927c0595e5a792d8bbab8b92/nova/api/openstack/compute/server_migrations.py#L135
>
> That said, if it is somehow allowing showing any other migration type
> than live-migration, it is a bug.
>
> [snip]
>
> -melwitt



More information about the openstack-discuss mailing list