Bug 1621421

Summary:	[RFE] indicate vNIC is out of sync on network QoS modification on engine
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Abhishekh Patil <abpatil>
Component:	ovirt-engine	Assignee:	eraviv
Status:	CLOSED ERRATA	QA Contact:	Michael Burman <mburman>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.3	CC:	branpise, danken, dholler, eraviv, lsurette, mburman, michal.skrivanek, mperina, mtessun, srevivo, usurse
Target Milestone:	ovirt-4.4.6	Keywords:	FutureFeature
Target Release:	4.4.6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.6.4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-01 13:22:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1848986
Bug Blocks:	1113630

Description Abhishekh Patil 2018-08-23 15:46:03 UTC

Description of problem:
Network QoS does not reflect the changes when VM is running. It needs to complete power cycle the VM to reflect the changes.

How reproducible:
100%

Steps to Reproduce:
1.Create a new network QoS
2.Create vNic profile and assign the newly created network QoS
3.Assign vNic profile to vm 
4.Test the network speed using iperf/qperf/netcat/nc/ttcp
5.Now, edit the network QoS (change the inbound/outbound average value)
6.Test the network speed again to see if the changes are reflected as per 
  modified network QoS.
7.Power cycle the VM and test the network speed again, it reflects the changes.

Actual results:

Network QoS does not reflect the changes when VM is running.

Expected results:

It should reflect the network QoS changes when the VM is running.

Additional info:

Comment 1 Dan Kenigsberg 2018-08-29 07:42:02 UTC

As you have noticed, changes to vnic profile take place only after shutdown/restart, or unplug/plug. Worse, there is no visual indication that the running profile has not changed, and that the desired one is not applied yet.

I would like to see a warning triangle on such VMs, but I am not sure we have the capacity to do that soon.

Comment 2 Michal Skrivanek 2020-03-18 15:49:58 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 3 Michal Skrivanek 2020-03-18 15:52:34 UTC

This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly

Comment 4 Dominik Holler 2020-03-23 14:27:34 UTC

This RFE should be kept open, as long as bug 1113630 is.

Comment 5 Michal Skrivanek 2020-06-23 12:35:06 UTC

This request is not currently committed to 4.4.z, moving it to 4.5

Comment 9 Michael Burman 2021-04-21 11:54:38 UTC

Verified on - rhvm-4.4.6.5-447.gd80dda7.9.el8ev.noarch

Comment 13 errata-xmlrpc 2021-06-01 13:22:09 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 (Moderate: RHV Manager security update (ovirt-engine) [ovirt-4.4.6]), 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/RHSA-2021:2179