Bad EC2 tokens with Euca Tools gives incorrect error

Bug #814303 reported by Navraj Chohan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AppScale
New
Low
Unassigned

Bug Description

I tried to set my environment variables with new credentials and then use euca tools to start a EC2 cloud. I choose a keyname which was never used before. The tools complained that the tools need to be deleted first, but in fact the problem was because my credentials were not valid (Amazon somehow deleted my access key and secret key). What the tools should do is report the correct error.

Navraj-Chohans-MacBook-Air:bin nchohan$ ruby appscale-run-instances --infrastructure euca --machine ami-b59e59dc --test -v --keyname appscaleRaj543
About to start AppScale over a cloud environment with the euca tools with instance type m1.large.
The keyname you chose is already in the system. Please either run this tool again with the --force flag or run the following:
euca-delete-keypair appscaleRaj543

Me running it forced:
Navraj-Chohans-MacBook-Air:bin nchohan$ ruby appscale-run-instances --infrastructure euca --machine ami-b59e59dc --test -v --keyname appscaleRaj543 --force
About to start AppScale over a cloud environment with the euca tools with instance type m1.large.
Trying again. Saw this from euca-add-keypair: OptInRequired: You are not subscribed to this service. Please go to http://aws.amazon.com to subscribe.
Saw this from euca-delete-keypair: OptInRequired: You are not subscribed to this service. Please go to http://aws.amazon.com to subscribe.

Navraj Chohan (nchohan)
Changed in appscale:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.