You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran a set of commands that according to the readme.md/wiki should work. However, I ran into an issue that took several hours to resolve (described below). Long story short, the DEFAULT_REGION and DEFAULT_AMI defined in ec2/next_ec2.py have to be aligned with the EC2 defaults. The readme/wiki should indicate these changes, perhaps under a "Troubleshooting" wiki page.
> python next_ec2.py --key-pair=$KEY_PAIR --identity-file=$KEY_FILE launch testing2
ERROR:boto:400 Bad Request
ERROR:boto:<?xml version="1.0" encoding="UTF-8"?><Response><Errors><Error><Code>InvalidKeyPair.NotFound</Code><Message>The key pair 'SSkey' does not exist</Message></Error></Errors><RequestID>907c6818-8cbb-49fa-a912-2a5557cf7b11</RequestID></Response>
Traceback (most recent call last):
File "next_ec2.py", line 1210, in<module>main()
File "next_ec2.py", line 1202, in main
real_main()
File "next_ec2.py", line 1009, in real_main
(master_nodes, slave_nodes) = launch_cluster(conn, opts, cluster_name)
File "next_ec2.py", line 519, in launch_cluster
user_data=user_data_content)
File "/Users/scott/anaconda/envs/py27/lib/python2.7/site-packages/boto/ec2/image.py", line 329, in run
tenancy=tenancy, dry_run=dry_run)
File "/Users/scott/anaconda/envs/py27/lib/python2.7/site-packages/boto/ec2/connection.py", line 973, in run_instances
verb='POST')
File "/Users/scott/anaconda/envs/py27/lib/python2.7/site-packages/boto/connection.py", line 1208, in get_object
raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?><Response><Errors><Error><Code>InvalidKeyPair.NotFound</Code><Message>The key pair 'SSkey' does not exist</Message></Error></Errors><RequestID>907c6818-8cbb-49fa-a912-2a5557cf7b11</RequestID></Response
which eventually led to a spark-users mailing list which indicated that Spark only supports regions us-east. Because next_ec2.py uses a Spark startup script, I saw my default EC2 region as shown in this image:
(changing this changes the default keys/etc)
In ec2/next_ec2.py I then defined
DEFAULT_REGION='us-east-1'DEFAULT_AMI='ami-d05e75b8'# Ubuntu Server 14.04 LTS
which is different from the defaults and could launch a NEXT EC2 instance.
This issue can also be resolved by changing your default region to Oregon, the default region for the next_ec2.py script. That is, if this issue encountered, you can just change your region like below instead of editing the source:
The text was updated successfully, but these errors were encountered:
So we need to decide how we want to deal with this. Since AMI's are tied to regions, we should have some logic that if a region is specified, an AMI must be specified as well.
In addition, let's try to try catch and connections with boto and put slightly more informative error messages. For example "Your key file did not work. Are you sure you are in the us-west region?" or something like that.
I ran a set of commands that according to the readme.md/wiki should work. However, I ran into an issue that took several hours to resolve (described below). Long story short, the
DEFAULT_REGION
andDEFAULT_AMI
defined inec2/next_ec2.py
have to be aligned with the EC2 defaults. The readme/wiki should indicate these changes, perhaps under a "Troubleshooting" wiki page.This last command produced the following output:
which eventually led to a spark-users mailing list which indicated that Spark only supports regions us-east. Because
next_ec2.py
uses a Spark startup script, I saw my default EC2 region as shown in this image:(changing this changes the default keys/etc)
In
ec2/next_ec2.py
I then definedwhich is different from the defaults and could launch a NEXT EC2 instance.
This issue can also be resolved by changing your default region to Oregon, the default region for the
next_ec2.py
script. That is, if this issue encountered, you can just change your region like below instead of editing the source:The text was updated successfully, but these errors were encountered: