yahoo-eng-team team mailing list archive

[OpenStack Infra <1947547@xxxxxxxxxxxxxxxxxx>]

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 <rsafrono@xxxxxxxxxx>
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


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1947547

Title:
  Sporadic metadata issues when creating OVN migration workload

Status in neutron:
  Fix Released

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1947547/+subscriptions