Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1077684

Summary:	Can't configure vNIC QoS to "unlimited" once it had been set
Product:	[Retired] oVirt	Reporter:	Lior Vernia <lvernia>
Component:	ovirt-engine-core	Assignee:	Lior Vernia <lvernia>
Status:	CLOSED CURRENTRELEASE	QA Contact:	GenadiC <gcheresh>
Severity:	medium	Docs Contact:
Priority:	high
Version:	3.4	CC:	asegurap, bazulay, gklein, iheim, obasan, rbalakri, s.kieske, yeylon
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	network
Fixed In Version:	ovirt-engine-3.5.0_beta	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1102646 (view as bug list)		Environment:
Last Closed:	2014-10-17 12:26:50 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:
Bug Blocks:	1102646

Description Lior Vernia 2014-03-18 12:18:41 UTC

Description of problem:

After setting the QoS of a vNIC, then changing it to "unlimited" (say by choosing another profile), the previous QoS values are retained.


Version-Release number of selected component (if applicable):

oVirt 3.4 (probably been around since 3.3).


How reproducible:

Always.


Steps to Reproduce:
1. Create profile with inbound and outbound bandwidth capping, assign this profile to a vNIC.
2. Create another profile without bandwidth capping, edit the vNIC and assign it this new profile.
3. Run "virsh dumpxml" on the VM.

Actual results:

the QoS limitations of the first profile are still there.


Expected results:

No bandwidth member for the vNIC should appear.


Additional info:

Comment 1 Antoni Segura Puimedon 2014-03-20 13:00:24 UTC

vdsm expects to receive an empty dictionary to clear out the inbound or outbound settings, if nothing is received it keeps the current settings of the vNIC.

Comment 2 Sandro Bonazzola 2014-05-08 13:38:44 UTC

This is an automated message

oVirt 3.4.1 has been released:
 * should fix your issue
 * should be available at your local mirror within two days.

If problems still persist, please make note of it in this bug report.

Comment 3 GenadiC 2014-07-08 10:50:59 UTC

Verified in 3.5.0-0.0.master.20140629172257.git0b16ed7.el6

Comment 4 Sandro Bonazzola 2014-10-17 12:26:50 UTC

oVirt 3.5 has been released and should include the fix for this issue.