Bug 1888567 - [16.1] Support north-south traffic with SR-IOV on VLAN tenant networks [NEEDINFO]
Summary: [16.1] Support north-south traffic with SR-IOV on VLAN tenant networks
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
Target Milestone: z4
: ---
Assignee: OSP Team
QA Contact: Eran Kuris
Depends On:
Blocks: 1826364
TreeView+ depends on / blocked
Reported: 2020-10-15 08:34 UTC by Roman Safronov
Modified: 2021-07-13 12:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:
jamsmith: needinfo? (jlibosva)

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Launchpad 1875852 0 None None None 2020-10-15 10:17:28 UTC

Description Roman Safronov 2020-10-15 08:34:54 UTC
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):

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:

Comment 2 Jakub Libosvar 2020-10-15 10:17:29 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.