Bug 692009 - Not able to add same account under two different providers
Summary: Not able to add same account under two different providers
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: alpha
Assignee: Richard Su
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks: ce-beta
TreeView+ depends on / blocked
 
Reported: 2011-03-30 07:26 UTC by Shveta
Modified: 2012-01-26 12:29 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)
err (68.12 KB, image/png)
2011-04-06 12:52 UTC, Shveta
no flags Details
ss (46.55 KB, image/png)
2011-04-06 14:02 UTC, wes hayutin
no flags Details
Screenshot of added 2 the same provider accounts for different providers (58.63 KB, image/png)
2011-04-06 14:09 UTC, Jozef Zigmund
no flags Details

Description Shveta 2011-03-30 07:26:35 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1. Providers are pre populated now , ec2-us-east-1 , ec2-us-west-1, mock
2. Added an account under ec2-us-east-1 
3. Not able to add same account for ec2-us-west-1
  
According to my understanding , images built for these providers like ec2-us-east-1 will launch image in us-east of the account.

What if i want to launch an image in us-west of the same account ?

So i think we should be able to add same provider account for these two different provider realms.

Please clarify.

Actual results:


Expected results:


Additional info:

rpm -qa |grep aeolus
aeolus-conductor-doc-0.0.3-0.fc14.20110330022620gitf6ac7cb.x86_64
aeolus-conductor-0.0.3-0.fc14.20110330022620gitf6ac7cb.x86_64
aeolus-configure-2.0.0-5.fc14.20110329222647git4adde63.noarch
aeolus-conductor-debuginfo-0.0.3-0.fc1420110329092545gitfa26991.x86_64
aeolus-conductor-daemons-0.0.3-0.fc14.20110330022620gitf6ac7cb.x86_64

Comment 1 Richard Su 2011-03-31 00:15:48 UTC
From speaking with Scott, adding the same account to different provider realms should be supported. Adding Zosef to the cc list because the recent credentials change may have affected this.

Comment 2 Jozef Zigmund 2011-03-31 17:03:15 UTC
Buxfix with git commit hash fb8dc451fbdf8127d03623204e91bdfdef47dd95

Comment 3 Shveta 2011-04-06 07:10:01 UTC
Same account cannot be added under ec2-us-east-1 and ec2-us-west-1.

Comment 4 Jozef Zigmund 2011-04-06 09:50:37 UTC
(In reply to comment #3)
> Same account cannot be added under ec2-us-east-1 and ec2-us-west-1.

I tested it again, but from my point of view it is implemented right. You can add the same provider account (mean the same username, password,etc.) for different providers(ec2-us-east-1 and ec2-us-west-1), but provider accounts cannot have the same names.

Comment 5 Shveta 2011-04-06 10:50:54 UTC
So then how will i launch images in us-east and us-west of same account name .
ec2-us-east-1 is for images in us-east realm or not?
Please clarify if i am wrong.

Comment 6 wes hayutin 2011-04-06 12:25:37 UTC
Shveta, Jozef is referring to the first field in the provider account form, where you give the provider account a label/name to be used in the application.  That label/name can be any name, just not a duplicate to another provider account

Comment 7 Shveta 2011-04-06 12:52:10 UTC
Got it.

Tested it again.
I am not able to add provider with common Username (with different labels)

Comment 8 Shveta 2011-04-06 12:52:42 UTC
Created attachment 490265 [details]
err

Comment 9 wes hayutin 2011-04-06 14:02:07 UTC
Created attachment 490290 [details]
ss

Recreated Shveta's issue. this fails_qa

Comment 10 Jozef Zigmund 2011-04-06 14:09:19 UTC
Created attachment 490292 [details]
Screenshot of added 2 the same provider accounts for different providers

Comment 11 wes hayutin 2011-04-06 14:15:05 UTC
yes.. sorry... this is working as designed..

using the same ec2 credentials, a user can:
1. create us-east-1 provider account
2. create us-west-1 provider account

Comment 12 wes hayutin 2011-08-01 19:58:47 UTC
release pending...

Comment 13 wes hayutin 2011-08-01 19:59:11 UTC
release pending.. 2

Comment 14 wes hayutin 2011-08-01 19:59:40 UTC
release pending...

Comment 16 wes hayutin 2011-12-08 13:59:23 UTC
closing out old bugs

Comment 17 wes hayutin 2011-12-08 14:12:07 UTC
perm close


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