Bug 1375854

Summary: RBAC:List only those vms for which the user has access to for VM placement plan
Product: Red Hat CloudForms Management Engine Reporter: Aziza Karol <akarol>
Component: UI - OPSAssignee: Zita Nemeckova <znemecko>
Status: CLOSED ERRATA QA Contact: Ramesh A <rananda>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: hkataria, jhardy, mpovolny, obarenbo, rananda, simaishi
Target Milestone: GA   
Target Release: 5.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: rbac:ownership
Fixed In Version: 5.7.0.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-04 13:00:33 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
all vms listed none

Description Aziza Karol 2016-09-14 06:18:56 UTC
Created attachment 1200731 [details]
all vms listed

Description of problem:


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

How reproducible:
100%

Steps to Reproduce:
1. As Admin, Navigate to Settings ==> Configuration ==> Access Control
2. Create a new role with "VM & Template Access Restriction" as  "Only User Owned".  Make sure all the module access is given in "Product Features (Editing)" i.e., Everything is checked
3. Create a new group with the above role
4. Create a new user with the above group
5. Set 2 vm ownership for this user.
5. Login with the newly created user and navigate to optimize->planning 
6. In reference VM selection, select "ALL VMs" from the drop down list and then choose a VM.

Actual results:
all the VMs are displayed. see attached screenshot

Expected results:
user should not have access to other VMs for plan calculations. should have access to only 2 vms for which the ownership is set.

Comment 3 Zita Nemeckova 2016-09-19 08:40:10 UTC
https://github.com/ManageIQ/manageiq/pull/11349

Comment 4 Ramesh A 2016-10-05 08:06:28 UTC
Good to go.  Verified and working fine in 5.7.0.3.20160927165516_075d0f3

Comment 6 errata-xmlrpc 2017-01-04 13:00:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://rhn.redhat.com/errata/RHBA-2017-0012.html