Bug 1329224

Summary: [Host QoS] - It's not possible to set an anonymous QoS on a network via the setup networks
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: BLL.NetworkAssignee: Martin Mucha <mmucha>
Status: CLOSED CURRENTRELEASE QA Contact: Meni Yakove <myakove>
Severity: high Docs Contact:
Priority: medium    
Version: 4.0.0CC: alkaplan, bugs, danken, ylavi
Target Milestone: ovirt-4.0.1Keywords: Automation, Regression, ZStream
Target Release: 4.0.1.1Flags: rule-engine: ovirt-4.0.z+
rule-engine: blocker+
rule-engine: planning_ack+
rule-engine: devel_ack+
myakove: testing_ack+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: wrong code reuse Consequence: inability to add overriding QoS, since such override is not named, while validation asserted present name. Fix: used separate objects for QoS and anonymous, overriding QoS Result: OK.
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 06:25:06 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 2016-04-21 12:57:39 UTC
Description of problem:
[Host QoS] - It's not possible to set an Anonymous QoS on a network via the setup networks.

When trying to set Anonymous QoS and approve operation, operation canceled with error:
Error while executing action: 

orchid-vds1.qa.lab.tlv.redhat.com:
Cannot setup Networks. Invalid data center.
QoS name cannot be empty.

engine.log 

 2016-04-21 15:49:57,936 WARN  [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-13) [6f9f90a] Validation of action 'HostSetupNetworks' failed for user admin@internal. Reasons: VAR__ACTION__SETUP,VAR__TYPE__NETWORKS,ACTION_TYPE_FAILED_QOS_STORAGE_POOL_NOT_EXIST,QOS_NAME_NOT_NULL
2016-04-21 15:49:57,936 INFO  [org.ovirt.engine.core.bll.network.host.HostSetupNetworksCommand] (default task-13) [6f9f90a] Lock freed to object 'EngineLock:{exclusiveLocks='[47c576e4-7862-4a92-99d1-51ffe7dbc9e0=<HOST_NETWORK, ACTION_TYPE_FAILED_SETUP_NETWORKS_IN_PROGRESS>]', sharedLocks='null'}'


Version-Release number of selected component (if applicable):
4.0.0-0.0.master.20160404161620.git4ffd5a4.el7.centos

How reproducible:
100

Steps to Reproduce:
1. Attach network to host via setup networks and set Anonymous QoS on the network, try to approve operation


Actual results:
Operation canceled with error

Expected results:
Should work as expected

Comment 1 Red Hat Bugzilla Rules Engine 2016-04-21 13:00: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 2 Red Hat Bugzilla Rules Engine 2016-04-25 16:24:08 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 3 Sandro Bonazzola 2016-05-02 10:08:28 UTC
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.

Comment 4 Yaniv Lavi 2016-05-23 13:22:57 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 5 Yaniv Lavi 2016-05-23 13:25:27 UTC
oVirt 4.0 beta has been released, moving to RC milestone.

Comment 6 Meni Yakove 2016-07-02 07:48:25 UTC
rhevm-4.0.2-0.2.rc1.el7ev.noarch

Comment 7 Sandro Bonazzola 2016-07-19 06:25:06 UTC
Since the problem described in this bug report should be
resolved in oVirt 4.0.1 released on July 19th 2016, it has been closed with a
resolution of CURRENT RELEASE.

For information on the release, and how to update to this release, follow the link below.

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

http://www.ovirt.org/release/4.0.1/