Sporadic metadata issues when creating OVN migration workload

[Roman Safronov]

When starting OVN migration workload, some of the workload VMs (usually only one of them) is not accessible via ssh. As can be seen in console logs the VM is not able to retrieve metadata.
This is basically due to bug https://bugs.launchpad.net/neutron/+bug/1813787 - nova
starts vm faster then local dvr router is ready thus during the vm's boot
process when vm asks for metadata, there is (yet) no haproxy ready to process
those requests.
If I create router and attach subnet before starting VMs the issue does not happen. So it seems like the order of the workload creation should be changed.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/neutron/+/814357

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/814357
Committed: https://opendev.org/openstack/neutron/commit/d49ce1652d31fb884285ed30e39ec10ef40c864d
Submitter: "Zuul (22348)"
Branch: master

commit d49ce1652d31fb884285ed30e39ec10ef40c864d
Author: Roman Safronov <email address hidden>
Date: Mon Oct 18 09:23:08 2021 +0300

    Fix OVN migration workload creation order

    Currently workload VMs start before subnet is connected to router.
    When DVR is enabled this causes sometimes that one of the VMs is not
    able to get metadata.

    Closes bug: #1947547

    Change-Id: Ifd686d7ff452abd1226fbbc97f499e05102e4596

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/c/openstack/neutron/+/815618

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/victoria
Review: https://review.opendev.org/c/openstack/neutron/+/815619

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/neutron/+/815620

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/xena
Review: https://review.opendev.org/c/openstack/neutron/+/815621

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/815618
Committed: https://opendev.org/openstack/neutron/commit/a805f175aef2fb190c2c2362c360a81458e7094c
Submitter: "Zuul (22348)"
Branch: stable/ussuri

commit a805f175aef2fb190c2c2362c360a81458e7094c
Author: Roman Safronov <email address hidden>
Date: Mon Oct 18 09:23:08 2021 +0300

    Fix OVN migration workload creation order

    Currently workload VMs start before subnet is connected to router.
    When DVR is enabled this causes sometimes that one of the VMs is not
    able to get metadata.

    Closes bug: #1947547

    Change-Id: Ifd686d7ff452abd1226fbbc97f499e05102e4596
    (cherry picked from commit d49ce1652d31fb884285ed30e39ec10ef40c864d)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/815621
Committed: https://opendev.org/openstack/neutron/commit/d86a3cdfe77a4e7ca64b57f59000cf0145c7a01a
Submitter: "Zuul (22348)"
Branch: stable/xena

commit d86a3cdfe77a4e7ca64b57f59000cf0145c7a01a
Author: Roman Safronov <email address hidden>
Date: Mon Oct 18 09:23:08 2021 +0300

    Fix OVN migration workload creation order

    Currently workload VMs start before subnet is connected to router.
    When DVR is enabled this causes sometimes that one of the VMs is not
    able to get metadata.

    Closes bug: #1947547

    Change-Id: Ifd686d7ff452abd1226fbbc97f499e05102e4596
    (cherry picked from commit d49ce1652d31fb884285ed30e39ec10ef40c864d)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/815620
Committed: https://opendev.org/openstack/neutron/commit/fbf8cb9347af99803c3ca6019ef21e88b2ad21bc
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit fbf8cb9347af99803c3ca6019ef21e88b2ad21bc
Author: Roman Safronov <email address hidden>
Date: Mon Oct 18 09:23:08 2021 +0300

    Fix OVN migration workload creation order

    Currently workload VMs start before subnet is connected to router.
    When DVR is enabled this causes sometimes that one of the VMs is not
    able to get metadata.

    Closes bug: #1947547

    Change-Id: Ifd686d7ff452abd1226fbbc97f499e05102e4596
    (cherry picked from commit d49ce1652d31fb884285ed30e39ec10ef40c864d)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/815619
Committed: https://opendev.org/openstack/neutron/commit/5f5f2e073a20cee0b9db22cdd82e580d5c265f14
Submitter: "Zuul (22348)"
Branch: stable/victoria

commit 5f5f2e073a20cee0b9db22cdd82e580d5c265f14
Author: Roman Safronov <email address hidden>
Date: Mon Oct 18 09:23:08 2021 +0300

    Fix OVN migration workload creation order

    Currently workload VMs start before subnet is connected to router.
    When DVR is enabled this causes sometimes that one of the VMs is not
    able to get metadata.

    Closes bug: #1947547

    Change-Id: Ifd686d7ff452abd1226fbbc97f499e05102e4596
    (cherry picked from commit d49ce1652d31fb884285ed30e39ec10ef40c864d)

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/networking-ovn train-eol release.