Bug 867292 - Display appropriate error message when non-privileged user tries to import/create an image
Display appropriate error message when non-privileged user tries to import/cr...
Status: NEW
Product: CloudForms Cloud Engine
Classification: Red Hat
Component: aeolus-conductor (Show other bugs)
1.1.0
Unspecified Unspecified
high Severity low
: rc
: ---
Assigned To: Angus Thomas
Rehana
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-17 05:01 EDT by Rehana
Modified: 2012-10-17 11:34 EDT (History)
1 user (show)

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


Attachments (Terms of Use)

  None (edit)
Description Rehana 2012-10-17 05:01:52 EDT
Description of problem:


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


How reproducible:
100%

Steps to Reproduce:
1.Created a new user with global zone admin user role, say userA
2.login to conductor as user A
3.Move to administer -->cloud
4. click on import image/new image
  
Actual results:
Observed that the error message "Images cannot be imported. No Cloud Resource Provider Accounts are currently enabled for this Cloud" was displayed even though the cloud had provider accounts mapped

Expected results:
The user "global zone admin" does not have the privilege to view any provider account, this prevents the user from  import/ create new image 

So, it will be good to show appropriate error message like "Insufficient privilege to perform the operation" or so
 
Additional info:

rpm -qa | grep aeolus
aeolus-configure-2.8.9-1.el6cf.noarch
aeolus-conductor-0.13.18-1.el6cf.noarch
rubygem-aeolus-cli-0.7.4-1.el6cf.noarch
aeolus-conductor-doc-0.13.18-1.el6cf.noarch
aeolus-all-0.13.18-1.el6cf.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
aeolus-conductor-daemons-0.13.18-1.el6cf.noarch

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