Bug 1283280 - Tenant admin has rights to add providers but cannot see them
Tenant admin has rights to add providers but cannot see them
Status: CLOSED NOTABUG
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance (Show other bugs)
5.5.0
Unspecified Unspecified
high Severity high
: GA
: 5.5.0
Assigned To: Gregg Tanzillo
Dave Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-18 10:21 EST by Pavol Kotvan
Modified: 2015-11-24 11:25 EST (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-24 11:25:13 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: Bug
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screenshot - provider not displayed in list of providers once it is added (43.71 KB, image/png)
2015-11-18 10:22 EST, Pavol Kotvan
no flags Details

  None (edit)
Description Pavol Kotvan 2015-11-18 10:21:29 EST
Description of problem:
Tenant administrator cannot see added providers. List of providers is empty even after new provider is added successfully. 

Version-Release number of selected component (if applicable):
5.5.0.10-beta2.1.20151110134042_d6f5459

How reproducible:
always

Steps to Reproduce:
1. Create new tenant1admin
2. Create new group and assign tenant1admin and Tenant administrator role to it
3. Create tenant1admin user and assign him into tenant admin group
4. Login as tenant1 admin
5. Add new Amazon or RHOS provider

Actual results:
Provider is successfully added but is not shown in Cloud -> Providers.

Expected results:
Provider is visible after creation

Additional info:
Tested with Amazon and RHOS7-GA providers. Superadmin can see providers added by tenant1 administrator.
Comment 1 Pavol Kotvan 2015-11-18 10:22 EST
Created attachment 1096126 [details]
Screenshot - provider not displayed in list of providers once it is added

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