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

Bug 2280335

Summary:	[revert] No trunk port connectivity after migration revert
Product:	Red Hat OpenStack	Reporter:	Arnau Verdaguer <averdagu>
Component:	openstack-neutron	Assignee:	Arnau Verdaguer <averdagu>
Status:	CLOSED ERRATA	QA Contact:	Fiorella Yanac <fyanac>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	17.1 (Wallaby)	CC:	chrisw, fyanac, ihrachys, jlibosva, mariel, scohen
Target Milestone:	z4	Keywords:	Triaged
Target Release:	17.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-neutron-18.6.1-17.1.20240918120815.85ff760.el9ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-11-21 09:40:35 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:

Description Arnau Verdaguer 2024-05-14 08:57:58 UTC

Description of problem:
After a reverted migration with trunk ports, the OVS tbr bridges are not created

Version-Release number of selected component (if applicable):


How reproducible:
Run the revert process as described in the documentation 

Steps to Reproduce:
1.
2.
3.

Actual results:
tbr bridges are not created and trunk port still connected to br-int and subports are not created

Expected results:
tbr bridges are created and trunk and subports are attached to tbr bridge

Additional info:
Eventho I only debugged a single case I suspect it may not happen 100% of the time

Comment 13 errata-xmlrpc 2024-11-21 09:40:35 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 (RHOSP 17.1.4 bug fix and enhancement advisory), 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-2024:9974