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:
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 ***