Back to bug 2109985

Who When What Removed Added
Red Hat One Jira (issues.redhat.com) 2022-07-22 15:56:33 UTC Link ID Red Hat Issue Tracker OSP-17814
Haresh Khandelwal 2022-07-25 04:50:22 UTC CC hakhande
Haresh Khandelwal 2022-07-25 04:52:59 UTC Flags needinfo?(mnietoji)
Miguel Lavalle 2022-07-25 14:06:55 UTC Assignee ovs-team ralonsoh
CC mlavalle
Miguel Angel Nieto 2022-07-26 09:38:49 UTC Flags needinfo?(mnietoji)
Rodolfo Alonso 2022-07-26 10:26:09 UTC Assignee ralonsoh rhos-maint
CC scohen
Component openvswitch openstack-neutron
Priority unspecified high
Rodolfo Alonso 2022-07-26 10:26:17 UTC Assignee rhos-maint ralonsoh
CC ralonsoh
Rodolfo Alonso 2022-07-26 10:32:59 UTC Keywords Triaged
Rodolfo Alonso 2022-07-26 10:37:38 UTC Version 17.0 (Wallaby) 17.1(Wallaby)
Rodolfo Alonso 2022-07-26 10:38:53 UTC Blocks 2111015
Rodolfo Alonso 2022-07-26 11:04:18 UTC Status NEW POST
Rodolfo Alonso 2022-07-28 13:05:34 UTC Status POST MODIFIED
Fixed In Version openstack-neutron-18.5.1-1.20220728111248.80d408c.el9osttrunk
Rodolfo Alonso 2022-08-05 07:55:37 UTC Doc Type If docs needed, set a value Release Note
Doc Text Open vSwitch (OVS) does not support offloading OpenFlow rules that have the `skb_priority`, `skb_mark`, or output queue fields set. Those fields are needed to provide quality-of-service (QoS) support for virtio ports.
+
If you set a minimum bandwidth rule for a virtio port, the Neutron Open vSwitch agent marks the traffic of this port with a Packet Mark Field. As a result, this traffic cannot be offloaded, and it affects the traffic in other ports. If you set a bandwidth limit rule, all traffic is marked with the default 0 queue, which means no traffic can be offloaded.
+
As a workaround, if your environment includes OVS hardware offload ports, disable the packet marking in the nodes that require hardware offloading. After you disable the packet marking, it will not be possible to set rate limiting rules for virtio ports. However, differentiated services code point (DSCP) marking rules will still be available.
+
In the configuration file, set the `disable_packet_marking` flag to `true`. After you edit the configuration file, you must restart the `neutron_ovs_agent` container.
For example:
+
----
$ cat `/var/lib/config-data/puppet-generated/neutron/etc/neutron/plugins/ml2/openvswitch_agent.ini`
[ovs]
disable_packet_marking=True
----
OSP Team 2022-08-31 14:09:33 UTC Fixed In Version openstack-neutron-18.5.1-1.20220728111248.80d408c.el9osttrunk openstack-neutron-18.5.1-1.20220823091141.464e88f.el9ost
errata-xmlrpc 2022-11-29 14:54:05 UTC Status MODIFIED ON_QA
Eran Kuris 2022-11-30 06:48:48 UTC QA Contact ekuris mnietoji
Red Hat One Jira (issues.redhat.com) 2022-11-30 07:09:38 UTC Link ID Red Hat Issue Tracker NFV-2731
Eran Kuris 2023-01-09 08:30:42 UTC Target Milestone --- ga
Target Release --- 17.1
CC ekuris
Miguel Angel Nieto 2023-05-16 07:54:44 UTC Status ON_QA VERIFIED
Jenny-Anne Lynch 2023-06-07 11:51:10 UTC Doc Type Release Note Known Issue
Flags needinfo?(ralonsoh)
CC jelynch
Doc Text Open vSwitch (OVS) does not support offloading OpenFlow rules that have the `skb_priority`, `skb_mark`, or output queue fields set. Those fields are needed to provide quality-of-service (QoS) support for virtio ports.
+
If you set a minimum bandwidth rule for a virtio port, the Neutron Open vSwitch agent marks the traffic of this port with a Packet Mark Field. As a result, this traffic cannot be offloaded, and it affects the traffic in other ports. If you set a bandwidth limit rule, all traffic is marked with the default 0 queue, which means no traffic can be offloaded.
+
As a workaround, if your environment includes OVS hardware offload ports, disable the packet marking in the nodes that require hardware offloading. After you disable the packet marking, it will not be possible to set rate limiting rules for virtio ports. However, differentiated services code point (DSCP) marking rules will still be available.
+
In the configuration file, set the `disable_packet_marking` flag to `true`. After you edit the configuration file, you must restart the `neutron_ovs_agent` container.
For example:
+
----
$ cat `/var/lib/config-data/puppet-generated/neutron/etc/neutron/plugins/ml2/openvswitch_agent.ini`
[ovs]
disable_packet_marking=True
----
Currently, Open vSwitch (OVS) does not support offloading OpenFlow rules that have the `skb_priority`, `skb_mark`, or output queue fields set. These fields are required for Quality of Service (QoS) support for virtio ports.
+
If you set a minimum bandwidth rule for a virtio port, the Networking service (neutron) OVS agent marks the traffic of this port with a Packet Mark field. This traffic cannot be offloaded, and it affects the traffic in other ports. If you set a bandwidth limit rule, all traffic is marked with the default 0 queue, which means that no traffic can be offloaded.
+
Workaround: If your environment includes OVS hardware offload ports, disable packet marking in the nodes that require hardware offloading. When you disable packet marking, it is not possible to set rate limiting rules for virtio ports. However, differentiated services code point (DSCP) marking rules are still available.
+
In the configuration file, set the `disable_packet_marking` flag to `true`. When you edit the configuration file, you must restart the `neutron_ovs_agent` container.
For example:
+
----
$ cat `/var/lib/config-data/puppet-generated/neutron/etc/neutron/plugins/ml2/openvswitch_agent.ini`
[ovs]
disable_packet_marking=True
----
Rodolfo Alonso 2023-06-07 13:14:44 UTC Flags needinfo?(ralonsoh)
James Smith 2023-06-13 17:30:31 UTC Flags needinfo?(ralonsoh) needinfo?(ekuris)
CC jamsmith
James Smith 2023-06-14 03:12:20 UTC Doc Text Currently, Open vSwitch (OVS) does not support offloading OpenFlow rules that have the `skb_priority`, `skb_mark`, or output queue fields set. These fields are required for Quality of Service (QoS) support for virtio ports.
+
If you set a minimum bandwidth rule for a virtio port, the Networking service (neutron) OVS agent marks the traffic of this port with a Packet Mark field. This traffic cannot be offloaded, and it affects the traffic in other ports. If you set a bandwidth limit rule, all traffic is marked with the default 0 queue, which means that no traffic can be offloaded.
+
Workaround: If your environment includes OVS hardware offload ports, disable packet marking in the nodes that require hardware offloading. When you disable packet marking, it is not possible to set rate limiting rules for virtio ports. However, differentiated services code point (DSCP) marking rules are still available.
+
In the configuration file, set the `disable_packet_marking` flag to `true`. When you edit the configuration file, you must restart the `neutron_ovs_agent` container.
For example:
+
----
$ cat `/var/lib/config-data/puppet-generated/neutron/etc/neutron/plugins/ml2/openvswitch_agent.ini`
[ovs]
disable_packet_marking=True
----
Currently, in ML2/OVS deployments, Open vSwitch (OVS) does not support offloading OpenFlow rules that have the `skb_priority`, `skb_mark`, or output queue fields set. These fields are required for Quality of Service (QoS) support for virtio ports.
+
If you set a minimum bandwidth rule for a virtio port, the Networking service (neutron) OVS agent marks the traffic of this port with a Packet Mark field. This traffic cannot be offloaded, and it affects the traffic in other ports. If you set a bandwidth limit rule, all traffic is marked with the default 0 queue, which means that no traffic can be offloaded.
+
Workaround: If your environment includes OVS hardware offload ports, disable packet marking in the nodes that require hardware offloading. When you disable packet marking, it is not possible to set rate limiting rules for virtio ports. However, differentiated services code point (DSCP) marking rules are still available.
+
In the configuration file, set the `disable_packet_marking` flag to `true`. When you edit the configuration file, you must restart the `neutron_ovs_agent` container.
For example:
+
----
$ cat `/var/lib/config-data/puppet-generated/neutron/etc/neutron/plugins/ml2/openvswitch_agent.ini`
[ovs]
disable_packet_marking=True
----
CC bcafarel
Flags needinfo?(bcafarel)
James Smith 2023-06-14 03:16:43 UTC Flags needinfo?(ralonsoh)
Bernard Cafarelli 2023-06-14 06:58:33 UTC Flags needinfo?(bcafarel)
Eran Kuris 2023-06-14 07:23:11 UTC Flags needinfo?(ekuris)
Rodolfo Alonso 2023-06-14 21:08:39 UTC Flags needinfo?(ralonsoh) needinfo?(ralonsoh)
Jenny-Anne Lynch 2023-07-19 12:18:05 UTC CC jelynch
Ian Frangs 2023-08-03 15:46:23 UTC Flags needinfo?(ralonsoh)
Bernard Cafarelli 2023-08-09 08:45:08 UTC Flags needinfo?(ralonsoh)
James Smith 2023-08-15 18:25:48 UTC Flags needinfo?(ralonsoh)
errata-xmlrpc 2023-08-16 00:03:01 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2023-08-16 01:11:24 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2023-08-16 01:11:24 UTC
errata-xmlrpc 2023-08-16 01:11:57 UTC Link ID Red Hat Product Errata RHEA-2023:4577
Rodolfo Alonso 2023-08-16 14:17:01 UTC Flags needinfo?(ralonsoh)

Back to bug 2109985