Bug 1077684 - Can't configure vNIC QoS to "unlimited" once it had been set
Summary: Can't configure vNIC QoS to "unlimited" once it had been set
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 3.5.0
Assignee: Lior Vernia
QA Contact: GenadiC
URL:
Whiteboard: network
Depends On:
Blocks: 1102646
TreeView+ depends on / blocked
 
Reported: 2014-03-18 12:18 UTC by Lior Vernia
Modified: 2016-02-10 19:38 UTC (History)
8 users (show)

Fixed In Version: ovirt-engine-3.5.0_beta
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1102646 (view as bug list)
Environment:
Last Closed: 2014-10-17 12:26:50 UTC
oVirt Team: Network
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 25950 0 master MERGED engine: Serialize null QoS to empty dictionary entry Never
oVirt gerrit 26736 0 ovirt-engine-3.4 MERGED engine: Serialize null QoS to empty dictionary entry Never
oVirt gerrit 28255 0 master MERGED engine: Persist empty QoS for VM Never
oVirt gerrit 28652 0 ovirt-engine-3.4 MERGED engine: Persist empty QoS for VM Never

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.
Note You need to log in before you can comment on or make changes to this bug.