Trunk subport's port status and binding:host_id don't updated after live-migration

[Slawek Kaplonski]

It happens for me in ml2/ovs env for sure.

How to reproduce the issue:

1. Create trunk with some subport,
2. Spawn vm with plugged to the trunk's parent port,
3. Check status of trunk's parent port and subport's port - both are ACTIVE and have correct host_id,
4. Live-migrate vm
5. Check status of trunk's parent port and subport's port - subport is DOWN and has old host_id.

Due to that, if e.g. dvr and l2pop are used, connectivity to such subport is broken.
To fix it I needed to restart neutron-ovs-agent on the host to which vm was migrated to.

[Lajos Katona (lajos-katona)]

Proposed fix: https://review.opendev.org/c/openstack/neutron/+/774245

[Lajos Katona (lajos-katona)]

WIP tempest test is here:
https://review.opendev.org/c/openstack/tempest/+/774689

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 15.3.3 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 16.3.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 17.1.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron 18.0.0.0rc1 release candidate.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/775103
Committed: https://opendev.org/openstack/neutron/commit/d570871e57f6d65c1eedad902754aa098a942829
Submitter: "Zuul (22348)"
Branch: stable/rocky

commit d570871e57f6d65c1eedad902754aa098a942829
Author: Slawek Kaplonski <email address hidden>
Date: Fri Feb 5 13:32:23 2021 +0100

    Fix update of trunk subports during live migration

    During the live migration trunk subports where updated only based
    on the "host_id" field. But when rpc message to update subports
    is send trunk's port is still bound to the old host and has
    "migrating_to" field in binding:profile set to the new host.
    Because of that binding:host_id for the subport's port wasn't updated
    proberly and port was set to DOWN on the new host.
    That could even cause connectivity break if L2population is used in the
    cloud.

    This patch fixes that by updating subport's binding:host_id field based
    on the migrating_to field if that is available and not empty.

    Closes-Bug: #1914747
    Change-Id: I98e55242d381ada642ca0729e9aefdea7628c945
    (cherry picked from commit e05101c8ac953cc2823b35aaed3d499afc101988)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron queens-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron rocky-eol release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/neutron stein-eol release.