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.
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.
adding to ce-beta tracker
moving bugs to cloud engine project
I'm trying to reproduce this, but it seems that this issue was resolved.
Verified Username and Password is Access Key and Secret Access key respectively.
release pending...
perm close
closing out old bugs