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

Bug 2236202

Summary:	[OVN migration] Trunk subport connectivity is broken on a VM live-migrated back to original node
Product:	Red Hat OpenStack	Reporter:	Roman Safronov <rsafrono>
Component:	openstack-neutron	Assignee:	Jakub Libosvar <jlibosva>
Status:	CLOSED DUPLICATE	QA Contact:	Eran Kuris <ekuris>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	17.1 (Wallaby)	CC:	averdagu, chrisw, dhughes, jjung, scohen
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-05 16:35:42 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 Roman Safronov 2023-08-30 16:15:20 UTC

Description of problem:
On an OVN environment that was migrated from OVS, trunk subports become not accessible after 2 live migrations i.e. migration to another node and then back to original node.

The issue did not happen on  RHOS-17.1-RHEL-9-20230802.n.1

Version-Release number of selected component (if applicable):
RHOS-17.1-RHEL-9-20230824.n.1

How reproducible:
100%, tried ovn migration with trunk ports already several times and in all cases ovn migration validation validate-workload-operations.test_live_migration_vm_with_trunk_back failed due to connectivity issue with trunk sub-ports 

Steps to Reproduce:

1. Deploy an HA environment with OVS neutron driver 
2. Create external network, create security group, create VMs with trunk ports and connect to the external network. 
3. Perform migration of neutron backend to ovn according to the official procedure
https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html/migrating_to_the_ovn_mechanism_driver/migrating-ovs-to-ovn
4. After ovs->ovn migration is completed live migration a VM with trunk port to another host, then live-migrate it back to the original node

Actual results:
trunk subports connectivity is broken after second live migration i.e. no response on ping requests from trunk subport on another VM after a VM is migrated back to original node

Expected results:
ping via trunk subports is working without issues after migrating back to original node

Additional info:

Comment 6 Jakub Libosvar 2023-09-05 16:35:42 UTC

This is caused by live migration introducing host value to ml2_port_bindings table. The subports need to have it empty or updated. This is a duplicate bug of bug 2236539.

*** This bug has been marked as a duplicate of bug 2236539 ***