Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2014965

Summary: Sporadic metadata issues when creating OVN migration workload
Product: Red Hat OpenStack Reporter: Roman Safronov <rsafrono>
Component: python-networking-ovnAssignee: Roman Safronov <rsafrono>
Status: CLOSED ERRATA QA Contact: Roman Safronov <rsafrono>
Severity: high Docs Contact:
Priority: high    
Version: 16.2 (Train)CC: apevec, ekuris, lhh, lmartins, majopela, scohen, spower
Target Milestone: z2Keywords: AutomationBlocker, Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-networking-ovn-7.4.2-2.20220107154846.3675681.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2017524 (view as bug list) Environment:
Last Closed: 2022-03-23 22:12:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2017524    

Description Roman Safronov 2021-10-18 06:43:24 UTC
Description of problem:
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.

Version-Release number of selected component (if applicable):
RHOS-16.2-RHEL-8-20211013.n.1
python3-networking-ovn-migration-tool-7.4.2-2.20210601204829

How reproducible:
Happens occassionally, about 20% of time

Steps to Reproduce:
Run OVN migration on DVR environment

Actual results:
One of the workload VMs is not able receive metadata. Downstream CI fails.

Expected results:
All workload VMs receive metadata successfully.

Additional info:

Comment 5 spower 2021-11-01 16:28:25 UTC
TRAC do not see this as a blocker as it has workarounds and OVN migration needs contact to support first. Asking for update in docs

Comment 6 Eran Kuris 2021-11-02 08:11:47 UTC
(In reply to spower from comment #5)
> TRAC do not see this as a blocker as it has workarounds and OVN migration
> needs contact to support first. Asking for an update in docs

thanks Sarah

Comment 11 Roman Safronov 2022-02-07 13:44:25 UTC
Verified on puddle RHOS-16.2-RHEL-8-20220201.n.1 which uses  python3-networking-ovn-migration-tool-7.4.2-2.20220113214852.a2eba10.el8ost.noarch

Verified that the rpm contains the fix and the OVN migration workload VMs do not have problems with retrieving metadata. The VMs are accessible via ssh without any issues.

Comment 18 errata-xmlrpc 2022-03-23 22:12:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 16.2.2), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1001