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
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.
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.
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
rhevm-4.0.2-0.2.rc1.el7ev.noarch
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/