Bug 679890

Summary: [UI] Incorrect label "Username" and "Password" on "New Account Provider" form
Product: [Retired] CloudForms Cloud Engine Reporter: Greg Blomquist <gblomqui>
Component: aeolus-conductorAssignee: Jozef Zigmund <jzigmund>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 0.3.1CC: dajohnso, deltacloud-maint, jzigmund, ssachdev
Target Milestone: alpha   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 684278    

Description Greg Blomquist 2011-02-23 19:23:30 UTC
Description of problem:

The "Username" field label on the "New Account Provider" form should actually read "AWS Access Key ID".

When creating a new Provider Account for EC2, I tried putting in my EC2 username in the "Username" field and receiving the "Invalid Account Details" error.  When checking the deltacloud-core logs, I see that the value I entered for "Username" is being sent to ec2 as "AWSAccessKeyID".

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

$ rpm -qa | grep deltacloud
deltacloud-aggregator-doc-0.0.3-0.fc14.i686
libdeltacloud-0.6-1.fc14.i686
rubygem-deltacloud-core-0.2.0-2.fc14.noarch
rubygem-deltacloud-image-builder-agent-0.0.7-1.fc14.noarch
deltacloud-aggregator-daemons-0.0.3-0.fc14.i686
rubygem-deltacloud-client-0.1.0-2.fc14.noarch
deltacloud-aggregator-0.0.3-0.fc14.i686
deltacloud-configure-2.0.0-3.fc14.noarch

How reproducible:

Happens whenever I enter the wrong value for "Username". :)

Steps to Reproduce:
1. Navigate to http://${HOST}/deltacloud/admin/provider_accounts
2. Click "New Account" button
3. Enter your EC2 username in the "Username" field and fill out the rest of the fields correctly
  
Actual results:

Receive the "Invalid Account Details" error.


Expected results:

The "Username" field should read "AWS Account Key ID" to prompt the user to enter the correct value into that field.


Additional info:

Is it possible that the "New Account Provider" form will change for different providers?  If so, then this probably needs to be specific for only EC2 provider accounts.

Comment 1 Greg Blomquist 2011-02-25 20:15:39 UTC
Updated the summary.

The password field label should read "AWS Secret Access Key" to prompt the user to enter the value required by the form.

Comment 2 wes hayutin 2011-03-22 13:01:48 UTC
adding to ce-beta tracker

Comment 3 wes hayutin 2011-06-15 12:12:57 UTC
moving bugs to cloud engine project

Comment 4 Jozef Zigmund 2011-06-21 10:13:14 UTC
I'm trying to reproduce this, but it seems that this issue was resolved.

Comment 5 Shveta 2011-07-12 12:05:07 UTC
Verified 

Username and Password is Access Key and Secret Access key respectively.

Comment 6 wes hayutin 2011-08-01 19:57:00 UTC
release pending...

Comment 7 wes hayutin 2011-08-01 19:58:21 UTC
release pending...

Comment 9 wes hayutin 2011-12-08 13:53:11 UTC
perm close

Comment 10 wes hayutin 2011-12-08 13:55:51 UTC
closing out old bugs