Bug 1538003 - Creating OpenStack Volume with user in a Tenant fails 403 Forbidden Server Error
Summary: Creating OpenStack Volume with user in a Tenant fails 403 Forbidden Server Error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.10.0
Assignee: Libor Pichler
QA Contact: Omri Hochman
URL:
Whiteboard:
Depends On:
Blocks: 1468726 1552821
TreeView+ depends on / blocked
 
Reported: 2018-01-24 09:44 UTC by Loic Avenel
Modified: 2019-02-11 14:09 UTC (History)
10 users (show)

Fixed In Version: 5.10.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1552821 (view as bug list)
Environment:
Last Closed: 2019-02-11 14:09:42 UTC
Category: ---
Cloudforms Team: Openstack
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot (208.91 KB, image/png)
2018-01-24 09:46 UTC, Loic Avenel
no flags Details

Description Loic Avenel 2018-01-24 09:44:42 UTC
Description of problem: Creating OpenStack Volume with user in a Tenant fails 403 Forbidden Server Error


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


How reproducible: always


Steps to Reproduce:
1. create user with limited access to Tenant
2. Go to Volumes
3. select Add new volume 

Actual results: fails with 


Expected results: Create Volumes


Additional info:

Comment 2 Loic Avenel 2018-01-24 09:46:17 UTC
Created attachment 1385360 [details]
screenshot

Comment 8 Satoe Imaishi 2018-03-07 19:50:41 UTC
Didn't realize https://github.com/ManageIQ/manageiq-ui-classic/pull/3341 isn't merged yet.

Do we need both PRs (https://github.com/ManageIQ/manageiq-api/pull/299 and https://github.com/ManageIQ/manageiq-ui-classic/pull/3341) for this BZ?  The ui-classic  PR also references this BZ and marked as blocker. Does this need to go back to ON_DEV?

Comment 9 Jad Haj Yahya 2018-07-16 06:51:56 UTC
Verified on 5.10.0.3


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