Unexpected EC2 error: An error occurred (VPCIdNotSpecified) when calling the DescribeSecurityGroups operation: No default VPC for this user

[data-steve]

I tried the dask-ec2 instructions again yesterday.

The default command will start 4 instances on us-east-1, but I’m not supposed to use that zone, since its most expensive. I think that’s why I’m can’t ssh into them.

>>> dask-ec2 up --keyname my-dev --keypair my-dev.pem
Launching nodes
DEBUG: Checking that keyname 'my-dev' exists on EC2
DEBUG: Checking that security group 'dask-ec2-default' exists on EC2
DEBUG: Creating 4 instances on EC2
DEBUG: Tagging instance 'i-01594434a277c32eb'
DEBUG: Tagging instance 'i-0c3908571ba92071b'
DEBUG: Tagging instance 'i-09bac6a9505f07752'
DEBUG: Tagging instance 'i-017c6aa768e3debb8'
Checking SSH connection to nodes
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 1/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 2/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 3/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 4/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 5/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 6/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 7/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 8/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 9/10 of function 'check_ssh' failed
DEBUG: Checking ssh connection for 54.152.58.253
DEBUG: Attempt 10/10 of function 'check_ssh' failed
ERROR: Retries limit exceeded

So then when I start using the —flag options to get more what I need, that’s when I get failing errors.

>>> dask-ec2 up --keyname my-dev --keypair my-dev.pem --region-name us-west-2
A file named cluster.yaml already exists, proceding will overwrite this file. Continue? [y/N]: y
Launching nodes
DEBUG: Checking that keyname 'my-dev' exists on EC2
DEBUG: Checking that security group 'dask-ec2-default' exists on EC2
Unexpected EC2 error: An error occurred (VPCIdNotSpecified) when calling the DescribeSecurityGroups operation: No default VPC for this user

When I try to supply it with VPC via the —vip-id or --security-group-id and --subnet-id info from other instances I’ve spun up manually, I get errors saying no such flag even though it is on the GitHub documentation

>>> dask-ec2 up --keyname my-dev --keypair my-dev.pem --region-name us-west-2 --ami ami-b52780d5 --vpc-id vpc-ae6e3bca --security-group  MLgroup --subnet-id subnet-bd1785cb
Error: no such option: --vpc-id

Oh, now I see that running dask-ec2 up —help shows that the api has changed and some of the flags have been removed.

Even after updating to the new api, I still get the error

>>> dask-ec2 up --keyname my-dev --keypair my-dev.pem --region-name us-west-2 --ami ami-b52780d5 --security-group MLgroup
A file named cluster.yaml already exists, proceding will overwrite this file. Continue? [y/N]: y
Launching nodes
DEBUG: Checking that keyname 'my-dev' exists on EC2
DEBUG: Checking that security group 'MLgroup' exists on EC2
Unexpected EC2 error: An error occurred (VPCIdNotSpecified) when calling the DescribeSecurityGroups operation: No default VPC for this user

Is this an error on my EC2 security group setup or something?

[jcrist]

Thanks for the bug report. Can you report your versions for python, dask_ec2, boto3, and paramiko, as well as what OS you're using?

$ python --version
Python 3.5.4 :: Continuum Analytics, Inc.
$ python -c "[print('%s: %s' % (m, __import__(m).__version__)) for m in ['dask_ec2', 'boto3', 'paramiko']]"
dask_ec2: 0.5.0
boto3: 1.4.1
paramiko: 2.1.2

[data-steve]

Thanks and sorry,

$ python --version Python 2.7.13 :: Anaconda custom (x86_64)

dask_ec2: v0.3.0 boto3: 1.4.4 paramiko: 2.1.2

Mac OS Sierra v 10.12.6

~ Steve

Sent via telepathy

On Sep 19, 2017, at 12:04 PM, Jim Crist notifications@github.com wrote:

Thanks for the bug report. Can you report your versions for python, dask_ec2, boto3, and paramiko, as well as what OS you're using?

$ python --version Python 3.5.4 :: Continuum Analytics, Inc. $ python -c "[print('%s: %s' % (m, import(m).version)) for m in ['dask_ec2', 'boto3', 'paramiko']]" dask_ec2: 0.5.0 boto3: 1.4.1 paramiko: 2.1.2 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dask/dask-ec2/issues/101#issuecomment-330588579, or mute the thread https://github.com/notifications/unsubscribe-auth/AHefi5r16GP4o-J3BwfP96uk0PjecVsEks5sj-YpgaJpZM4Pcnlc.

[jcrist]

Your version of dask-ec2 is very outdated. Can you try again with a newer install?

pip install -U dask-ec2

[data-steve]

your wisdom exceeds mine.