Description of problem: During migration to OVN on SR-IOV env after FFU the VMs with VF(direct) ports became not pingable. Migration process itself completed successfully and normal ports were pingable. Note, the issue did not happen when I ran OVN migration on a freshly installed SR-IOV env. Version-Release number of selected component (if applicable): RHOS-16.1-RHEL-8-20201007.n.0 puppet-ovn-15.4.1-0.20200311045730.192ac4e.el8ost.noarch python3-networking-ovn-7.3.1-1.20200902233412.4e24f4c.1.el8ost.noarch python3-networking-ovn-migration-tool-7.3.1-1.20200902233412.4e24f4c.1.el8ost.noarch How reproducible: Tried once and the issue occurred Steps to Reproduce: 1. Install OSP13 SR-IOV environment with ML2OVS mechanism driver 2. Perform FFU to OSP16.1 3. Create VM instances with normal and VF(direct) SR-IOV ports on each compute node. Create floating ip for each VM. 4. Perform OVN migration procedure. 5. Verify that all VMs are pingable via floating IPs. Actual results: normal VMs are pingable - CORRECT VMs with VF ports are not pingable - BUG Expected results: All VMs are pingable diring and after OVN migration procedure Additional info:
We looked with Rodolfo with Lucas' help at the environment and currently OVN doesn't support N/S traffic with SRIOV + VLAN tenant network: https://bugs.launchpad.net/neutron/+bug/1875852 We can use this BZ to track the limitation if we want to fix it in OSP. There is probably nothing to do in networking-ovn, the work should be done in core-OVN side.
[600 days old] This is the RFE https://bugzilla.redhat.com/show_bug.cgi?id=1826364 to support this functionality on 17 or 18. Closing this bug