Bug 1279771

Summary: [Host QoS] - Updating/changing value/s on the Host QoS entity via DC while a network that using this entity and attached to server doesn't invoke sync
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Martin Mucha <mmucha>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.6.0CC: bugs, danken, myakove, sbonazzo
Target Milestone: ovirt-4.1.0-betaFlags: rule-engine: ovirt-4.1+
rule-engine: planning_ack+
danken: devel_ack+
myakove: testing_ack+
Target Release: 4.1.0.2   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-01 14:49:49 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:

Description Michael Burman 2015-11-10 09:26:34 UTC
Description of problem:
[Host QoS] - Updating/changing value/s on the Host QoS entity via DC while a network that using this entity and attached to server doesn't invoke sync, cause setup networks command is not sent. 

Version-Release number of selected component (if applicable):
3.6.0.3-0.1.el6

How reproducible:
100

Steps to Reproduce:
1. Create Host QoS entity(weight - 50, rate - 500, commit - 300) via DC or via Networks tab while creating new network.
2. Attach the network with the QoS to host via Setup networks
3. Via DC, update/change the weight value to 50 on the Host QoS entity 

Actual results:
Network considered as out-of-sync. Setup networks command isn't sent and doesn't invoke sync. There is a difference between Host and DC.

Expected results:
Setup Networks command should be sent and network should be synced to host.

Comment 1 Dan Kenigsberg 2015-11-10 13:39:15 UTC
alkaplan told me that Engine simply does not issue a multihost command on this change (unlike what happens when MTU is changed in the DC level).

This should be fixed (but not necessarily during 3.6.z).

Comment 2 Michael Burman 2015-11-23 11:51:57 UTC
Martin,

Please note, that the fix for this bug should include scenario in which we removing a Host QoS entity from DC while network/s attached to host/s are using this QoS entity ^^ (As agreed with danken) .

For QA, to test such scenario. 

Thanks,

Comment 3 Red Hat Bugzilla Rules Engine 2015-11-30 22:37:38 UTC
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.

Comment 4 Mike McCune 2016-03-28 23:09:17 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 5 Michael Burman 2016-05-25 12:09:55 UTC
Tested on - 4.0.0-0.0.master.20160524171531.gitfba61e9.el7.centos and 
vdsm-4.18.0-43.git6f7fc83.el7.centos.x86_64

- Updating/changing values on the host QoS entity via DC while the network attached to host is working and invoking sync.

- Remove the host QoS entity from DC while the network is attached to the host isn't invoke sync and didn't fixed as agreed, see comment 2^^ 
Dan, do you want separate bug on that scenarion or should we keep going on this one? 

Thanks,

Comment 6 Michael Burman 2016-05-26 05:15:05 UTC
Martin, please fix and include the remove host QoS from DC scenario as well in this BZ. Thank you.

Comment 7 Red Hat Bugzilla Rules Engine 2016-05-26 05:15:11 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 8 Michael Burman 2016-12-05 13:02:07 UTC
Verified on - 4.1.0-0.2.master.20161204231323.gite9669ad.el7.centos