Back to bug 2109597

Who When What Removed Added
Ben Roose 2022-07-21 15:13:07 UTC CC broose
Mircea Vutcovici 2022-07-21 15:14:37 UTC CC apevec
Component openstack-neutron openvswitch
Assignee rhos-maint ovs-team
Red Hat One Jira (issues.redhat.com) 2022-07-21 15:15:52 UTC Link ID Red Hat Issue Tracker OSP-17784
Rodolfo Alonso 2022-07-29 08:39:11 UTC CC rosingh
Severity high urgent
Priority unspecified urgent
CC ralonsoh
Red Hat One Jira (issues.redhat.com) 2022-07-29 08:48:59 UTC Link ID Red Hat Issue Tracker NFV-2586
Haresh Khandelwal 2022-08-01 09:59:20 UTC CC hakhande
Haresh Khandelwal 2022-08-02 06:45:44 UTC Flags needinfo?(ralonsoh)
Rodolfo Alonso 2022-08-02 15:44:27 UTC Flags needinfo?(ralonsoh)
Haresh Khandelwal 2022-08-03 09:00:59 UTC Flags needinfo?(mircea.vutcovici)
Mircea Vutcovici 2022-08-03 20:22:43 UTC Flags needinfo?(mircea.vutcovici)
Haresh Khandelwal 2022-08-04 12:22:42 UTC CC mleitner
Flags needinfo?(mleitner)
Florin Boboc 2022-08-16 19:35:37 UTC CC fboboc
Haresh Khandelwal 2022-08-18 05:44:07 UTC Assignee ovs-team hakhande
Keywords Triaged
Doc Type If docs needed, set a value Release Note
Status NEW ASSIGNED
Haresh Khandelwal 2022-08-18 05:46:27 UTC Depends On 1986511
Doc Text There is HW limitation in CX5 and cannot be fixed.
Each flow has a "direction" in HW - tx or rx. If the source port of the flow is a VF it is considered as TX flow in HW and CX5 cannot pop VLAN on TX path. This prevents offloading the flow with pop_vlan action to the HW.
Haresh Khandelwal 2022-09-09 09:43:44 UTC Doc Type Release Note Known Issue
Haresh Khandelwal 2022-09-09 09:45:30 UTC CC mgeary
Flags needinfo?(mgeary)
Marcelo Ricardo Leitner 2022-10-07 18:24:43 UTC Blocks 2131355
Flags needinfo?(mleitner)
mgeary 2022-10-12 11:14:09 UTC Doc Text There is HW limitation in CX5 and cannot be fixed.
Each flow has a "direction" in HW - tx or rx. If the source port of the flow is a VF it is considered as TX flow in HW and CX5 cannot pop VLAN on TX path. This prevents offloading the flow with pop_vlan action to the HW.
There is a hardware limitation in CX-5 with no workaround.
Each flow has a direction in HW - TX or RX. If the source port of the flow is a VF, it is considered as TX flow in HW. CX-5 cannot pop VLAN on TX path which prevents offloading the flow with pop_vlan to the HW.
mgeary 2022-10-12 12:37:23 UTC Doc Text There is a hardware limitation in CX-5 with no workaround.
Each flow has a direction in HW - TX or RX. If the source port of the flow is a VF, it is considered as TX flow in HW. CX-5 cannot pop VLAN on TX path which prevents offloading the flow with pop_vlan to the HW.
There is a hardware (HW) limitation with CX-5.
Each flow has a direction in HW, either transmit (TX) or receive (RX). If the source port of the flow is a virtual function (VF), it is considered TX flow in HW. CX-5 cannot pop VLAN on TX path, which prevents offloading the flow with pop_vlan to the HW.
mgeary 2022-10-12 12:52:14 UTC Doc Text There is a hardware (HW) limitation with CX-5.
Each flow has a direction in HW, either transmit (TX) or receive (RX). If the source port of the flow is a virtual function (VF), it is considered TX flow in HW. CX-5 cannot pop VLAN on TX path, which prevents offloading the flow with pop_vlan to the HW.
There is a hardware (HW) limitation with CX-5. Every network traffic flow has a direction in HW, either transmit (TX) or receive (RX). If the source port of the flow is a virtual function (VF), then it is also TX flow in HW. CX-5 cannot pop VLAN on TX path, which prevents offloading the flow with pop_vlan to the HW.
James Smith 2022-11-09 22:05:04 UTC Flags needinfo?(mgeary) needinfo?(astillma)
CC astillma, jamsmith
James Smith 2022-11-09 22:24:24 UTC Flags needinfo?(hakhande) needinfo?(mgeary) needinfo?(astillma)
Haresh Khandelwal 2022-11-15 16:56:09 UTC Flags needinfo?(hakhande)
Marcelo Ricardo Leitner 2023-02-22 19:26:32 UTC Blocks 2172625
Marcelo Ricardo Leitner 2023-02-22 19:27:42 UTC Blocks 2131355
Lukas Svaty 2023-06-16 09:38:20 UTC CC ekuris
Flags needinfo?(ekuris) needinfo?(hakhande)
Eran Kuris 2023-06-18 12:46:05 UTC Flags needinfo?(ekuris) needinfo?(vkhitrin)
CC vkhitrin
Haresh Khandelwal 2023-06-19 07:09:35 UTC Flags needinfo?(hakhande)
Haresh Khandelwal 2023-06-19 07:17:15 UTC Target Release --- 17.1
Target Milestone --- z1
Status ASSIGNED ON_QA
RHEL Program Management 2023-06-19 07:17:27 UTC Target Release 17.1 17.0
Eran Kuris 2023-06-19 08:26:26 UTC QA Contact ekuris mnietoji
Eran Kuris 2023-06-19 08:27:39 UTC Flags needinfo?(vkhitrin)
RHEL Program Management 2023-06-27 14:09:26 UTC Target Release 17.0 17.1
Miguel Garcia 2023-06-27 14:18:52 UTC Flags needinfo?(hakhande)
Haresh Khandelwal 2023-06-28 11:37:21 UTC Flags needinfo?(hakhande)
Fixed In Version 5.14.0-284.11.1.el9_2.x86_64
Miguel Garcia 2023-06-28 14:59:53 UTC Keywords TestOnly
Miguel Angel Nieto 2023-07-03 10:41:27 UTC Status ON_QA VERIFIED
Jon Schlueter 2023-07-05 19:59:36 UTC Fixed In Version 5.14.0-284.11.1.el9_2.x86_64 kernel-5.14.0-284.11.1.el9_2
CC jschluet
Priscila Gutierres 2023-07-10 13:17:21 UTC CC prgutier
Ian Frangs 2023-08-03 15:46:23 UTC Flags needinfo?(hakhande)
Haresh Khandelwal 2023-08-04 12:13:45 UTC Flags needinfo?(hakhande)
Andy Stillman 2023-08-04 13:52:31 UTC Flags needinfo?(astillma) needinfo?(astillma)
Target Milestone z1 ga
James Smith 2023-08-15 18:20:50 UTC Status VERIFIED CLOSED
Flags needinfo?(hakhande)
Resolution --- NOTABUG
Last Closed 2023-08-15 18:20:50 UTC

Back to bug 2109597