Migrating a VM to a different host fails

[Ryu Ishimoto]

Starting in newton, VM migration to a different host fails with the following error message from the plugin in port update:

"BadRequest: Bad port request: The interface name was not provided or empty."

This is because the port update request contains the following data which the plugin rejects:

"{'binding:profile': {'migrating_to': 'compute-3'}}"

'migrating_to' attribute was introduced in nova in newton[1].

This issue was confirmed by a midonet user attempting a migration.

[1] https://github.com/openstack/nova/commit/55f3d476a12dce8a70d3e485f0f2f9c752cf

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/505234

[Dennis Kuhn (d.kuhn)]

I can confirm this bug for newton. The proposed fix solves the problem with the live migration for us.

We use python-networking-midonet 3.0.0-1

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/505234
Committed: https://git.openstack.org/cgit/openstack/networking-midonet/commit/?id=2a4f619829fc6125b5658b75dac8ebabab6e6711
Submitter: Zuul
Branch: stable/ocata

commit 2a4f619829fc6125b5658b75dac8ebabab6e6711
Author: YAMAMOTO Takashi <email address hidden>
Date: Tue Sep 19 20:46:29 2017 +0900

    v2 plugin: Relax the validation for binding:profile

    It can have other fields like "migrating_to".

    Note: This code doesn't exist in pike and later.

    Closes-Bug: #1718177
    Change-Id: If126b1c612761044e42512336ee87f8238f6d8db

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-midonet 4.1.0 release.