Bug 1191154 - Adding permission to multiple vms adds it only to the first one
Summary: Adding permission to multiple vms adds it only to the first one
Keywords:
Status: CLOSED DUPLICATE of bug 999719
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Pavel Stehlik
URL:
Whiteboard: ux
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-10 14:56 UTC by Petr Vobornik
Modified: 2015-02-11 13:36 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-11 13:36:21 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Petr Vobornik 2015-02-10 14:56:26 UTC
Description of problem:
Can't add role to multiple machines at once using Administration Portal.

Version-Release number of selected component (if applicable):
3.5.0-0.31.el6ev

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Administration Portal
2. Select multiple vms
3. Go to permissions tab
4. click on add button
5. in dialog search for desired LDAP user
6. select the user
7. choose UserVmManager role
8. click on OK button

Actual results:
UserVmManager role for selected user is added only to the first vm.


Expected results:
UserVmManager role for selected user is added to all selected vms.

Comment 1 Einav Cohen 2015-02-11 13:36:21 UTC
sub-tabs pertain to one (selected) item in the main-grid by definition (typically, the first one that was selected on the main-grid). 
consequently, operations from sub-tabs will pertain only to that single item in the main-grid. 

so this is by design, but I understand the user-experience issue here, and we will try to take care of that in the context of bug 999719 as part of the 4.0 UI overhaul. 

closing as duplicate.

*** This bug has been marked as a duplicate of bug 999719 ***


Note You need to log in before you can comment on or make changes to this bug.