Created attachment 1331315 [details] record2 Description of problem: [UI] - Edit/remove buttons are grayed out in the 'QoS' sub tab after creation and removal of a new QoS entity. After creating any QoS entity, the remove and edit buttons are grayed out for all QoS entities. Version-Release number of selected component (if applicable): 4.2.0-0.0.master.20170926175518.git0d20200.el7.centos How reproducible: Almost 100% I think there are some other scenarios which cause this result as well. Steps to Reproduce: 1. Create few QoS entities 2. Remove some 3. Create and remove QoS entities Actual results: In most of the times after few create and remove, the edit and remove buttons are grayed out and not available. I'm not sure exactly what cause this, but there is a bug there for sure. Sometimes the buttons are grayed out even without any action, just when entering the sub tab.
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.
Bug reproduced on - 4.2.0-0.0.master.20171002190603.git3015ada.el7.centos Shouldn't be ON_QA
3015ada is 35 commits after the one for the QoS buttons, so the build should contain the fix, so this is FailedQA. greg@dauntless:/home/greg/projects/ovirt-engine(:3015ada92f|✔) % noglob git log --oneline 110b62b^1..3015ada92f | tee /dev/tty | wc 3015ada92f engine : Several jobs are not finished b5269721b4 webadmin: Replace empty image with empty htmlString 452f4f94b2 core: Set imported Memory snapshot image to active cbd2465913 core: fix enabling fencing from API 6a19445ef2 engine: fix IllegalArgument during host edit e0c4d76726 core: optimize StorageHandlingCommandBase#initUnregisteredDisksToDB 204a1c2d7a core: optimize AttachStorageDomainToPoolCommand 4a77c2f4e8 core: make UnregisteredDisksDao a MassOperationsDao e71bc357cf core: introduce UnregisteredDiskId a1ade6cb07 core: remove unnecessary cast 1efb4b16e8 core: rm PostDeleteActionHandlerTest#inectorRule 9ae1be620d core: Change the limit of LVs per VG to 1300 11e1fb110e core: MetadataDiskDescriptionHandler CDI fe89063604 packaging: setup: Remove leftover external_truststore on new setups 75e5c704a3 core: @InjectMocks in FenceAgentExecutorTest 813c20faa7 core: FenceAgentExecutorTest's VDS 2de2bfb87e core: Remove FenceAgentExecutorTest#injectorRule 77227df802 core: FenceAgentExecutorTest constants 69a4d09cdb Revert "core: Add end procedure to DestroyImageCommand and DestroyImageCheckCommand" 20608cfd2f Revert "core: Retry failed live merge commands" 6a8d52c32b core: repair aggregateDiskImagesSnapshots. 7a743df38c core: AffinityRulesEnforcementManagerTest#injectorRule 3c8631e52c webadmin: rename "OpenStack Volume" 7e2fb8841b engine: fix validation message in cinder snapshots 007c3929a0 fix tiny English typo 78f2e95652 core: Add end procedure to DestroyImageCommand and DestroyImageCheckCommand 2a61355d24 Webadmin: Change CollapseSnapshots default value d807b7a06c webadmin: Add check if networkModel has vlan and it is not null 9f44eead45 core: fix testAggregateDiskImagesSnapshots 5c500971fe core: fix NPE when running VM with NUMA pinning dbdfeaa15d core: Restore snapshots constraints to base_disks dfcacf2c4c core: Restore image_templates_images constraint eb43c2f1d2 bll: Optimization - don't connect same targets in RunVM 98905e8a36 core: Add getter and setter for OpenstackNetworkProviderId to VDS 110b62bc1f webadmin: DC QoS fixes 35 229 2075
Michael, can you retry? It's working for me on master 9cd0c28 [assigning to Alexander, since he wrote the original fix]
(In reply to Greg Sheremeta from comment #4) > Michael, can you retry? It's working for me on master 9cd0c28 > > [assigning to Alexander, since he wrote the original fix] Hi Greg, Can't reproduce on 4.2.0-0.0.master.20171112130303.git8bc889c.el7.centos
Cool, thanks.
Verified on ovirt-engine-4.2.0-0.0.master.20171113223918.git25568c3.el7.centos.noarch
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.