Bug 1142865 - Missing QoS in the warning that is shown when removing multiple QoS
Summary: Missing QoS in the warning that is shown when removing multiple QoS
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: ---
Hardware: Unspecified
OS: Linux
low
unspecified
Target Milestone: ovirt-3.6.6
: 3.6.6
Assignee: Doron Fediuck
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-17 14:22 UTC by Daniel Erez
Modified: 2016-05-30 10:54 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-30 10:54:57 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-3.6.z+
mgoldboi: planning_ack+
dfediuck: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)
screenshot (166.25 KB, image/png)
2016-05-05 11:52 UTC, meital avital 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 46327 0 master MERGED webadmin: Fixed remove storage qos error popup 2016-04-04 08:03:48 UTC
oVirt gerrit 46328 0 ovirt-engine-3.6 MERGED webadmin: Fixed remove storage qos error popup 2016-04-21 12:13:21 UTC

Description Daniel Erez 2014-09-17 14:22:59 UTC 
Description of problem:
When trying to remove multiple QoSes where at least one is attached and one is not attached to a disk profile, the message that is shown should indicate all the QoSes that were selected.

Version-Release number of selected component (if applicable):
3.5

How reproducible:
100%

Steps to Reproduce:
1. Navigate to Datacenters and select a DC.
2. Navigate to QoS sub tab.
3. Create at least one QoS.
4. Navigate to Storage and select an item.
5. Navigate to the "Disk Profiles" subtab.
6. Create at least one profile (and attach it to a QoS).
7. Select both item that were created.
8. Click on remove.

Actual results:
The message does not include the QoS that is not attached to a disk profile.

Expected results:
The message should include all of the QoSes that were selected to be removed.

Additional info:
Comment 1 Sandro Bonazzola 2015-01-21 16:08:32 UTC 
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority
Comment 3 Tomer Saban 2015-08-30 12:32:04 UTC 
Should the user see the QoS which is safe to be removed even though it is not attached to any Disk Profile?
Comment 4 Moran Goldboim 2015-09-02 13:27:04 UTC 
(In reply to Tomer Saban from comment #3)
> Should the user see the QoS which is safe to be removed even though it is
> not attached to any Disk Profile?

we should indicate all the profile we are about to remove.
Comment 5 Red Hat Bugzilla Rules Engine 2015-10-19 10:53: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 6 Sandro Bonazzola 2015-10-26 12:33:01 UTC 
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015.
Please review this bug and if not a blocker, please postpone to a later release.
All bugs not postponed on GA release will be automatically re-targeted to

- 3.6.1 if severity >= high
- 4.0 if severity < high
Comment 7 Red Hat Bugzilla Rules Engine 2015-11-01 16:45:08 UTC 
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset.
Please set the correct milestone or add the z-stream flag.
Comment 8 Red Hat Bugzilla Rules Engine 2015-11-23 13:55: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 9 Mike McCune 2016-03-28 23:10:48 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 11 meital avital 2016-05-05 11:51:46 UTC 
Verified on version: 3.6.6-0.1.el6
See attach screenshot
Comment 12 meital avital 2016-05-05 11:52:37 UTC 
Created attachment 1154178 [details]
screenshot
Note You need to log in before you can comment on or make changes to this bug.