Bug 867964 - User not able to launch new image even when it has enabled Cloud Resource Provider Accounts associated with his cloud
Summary: User not able to launch new image even when it has enabled Cloud Resource Pro...
Keywords:
Status: CLOSED EOL
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-18 17:19 UTC by Shveta
Modified: 2020-03-27 18:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
mapped accounts (47.46 KB, image/png)
2012-10-18 17:19 UTC, Shveta
no flags Details
provider account (48.87 KB, image/png)
2012-10-18 17:19 UTC, Shveta
no flags Details

Description Shveta 2012-10-18 17:19:30 UTC
Created attachment 629569 [details]
mapped accounts

Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Login as admin , create a user "newuser" 
2. Global Role grants -- grant "cloud resource zone administrator " role to the user
3. login as user , create a new cloud and CRZ.
4. Map account -- user can't map provider accounts
5. login as admin map provider account to the user's cloud
6. Login as newuser try to launch new image :

It says: "Images cannot be built. There are no enabled Cloud Resource Provider Accounts associated with this Cloud. "
  
Actual results:


Expected results:


Additional info:

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

Comment 1 Shveta 2012-10-18 17:19:56 UTC
Created attachment 629570 [details]
provider account


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