Bug 1934096

Summary:	[OVN][QoS] Port inherited network QoS policy not honored
Product:	Red Hat OpenStack	Reporter:	Roman Safronov <rsafrono>
Component:	python-networking-ovn	Assignee:	Rodolfo Alonso <ralonsoh>
Status:	CLOSED ERRATA	QA Contact:	Roman Safronov <rsafrono>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.1 (Train)	CC:	apevec, egarciar, eolivare, jlibosva, lhh, majopela, scohen
Target Milestone:	z6	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-networking-ovn-7.3.1-1.20210329203525.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1967085 (view as bug list)		Environment:
Last Closed:	2021-05-26 13:51:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1546996, 1967085

Description Roman Safronov 2021-03-02 14:01:23 UTC

Description of problem:
When policy is created and attached to the network before VM is up (before port is active), it is not applied (no qos object in ovn nb db)

Version-Release number of selected component (if applicable):
puddle RHOS-16.1-RHEL-8-20210216.n.1

How reproducible:
100%

Steps to Reproduce:
1. Make sure you are using an environment with qos enabled
2. Create a network, create a qos policy and apply to the network, example commands
openstack network qos policy create bw-limiter
openstack network qos rule create --type bandwidth-limit --max-kbps 3000 --max-burst-kbits 2400 --egress bw-limiter
openstack network set --qos-policy bw-limiter

3. Launch 2 VMs on that network, wait until ports are ACTIVE then login to controller node and run 'ovn-nbctl list qos'


Actual results:
no qos objects in 'ovn-nbctl list qos' output - BUG
qos rule does not work

Expected results:
qos objects listed in 'ovn-nbctl list qos' output.
qos rules work

Additional info:
Note: I tried to launch RHEL VMs and ran iperf3 between the VMs (there was also security group allowing iperf traffic). The qos rule was not applied.
After I re-applied the rule after VMs are up, all worked as expected.

Comment 11 Roman Safronov 2021-04-14 13:15:28 UTC

Verified on RHOS-16.1-RHEL-8-20210413.n.0 which is using python3-networking-ovn-7.3.1-1.20210409093428.4e24f4c.el8ost.noarch
Verified that the problem does not happen. When we first create a qos policy and attach it to a network, and only then we create a VM, the policy is working properly for the VM.

Comment 18 errata-xmlrpc 2021-05-26 13:51:32 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 16.1.6 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:2097