dask / dask-ec2

Start a cluster in EC2 for dask.distributed
106 stars 37 forks source link

Unable to destroy a cluster #35

Closed deeplook closed 7 years ago

deeplook commented 8 years ago

I was recently testing a fresh github clone of dask-ec2, could perfectly create a cluster with default configuration, but not destroy it again with dark-ec2 destroy (apparently, the instances were not found, see message below), so I had to terminate the instances in the AWS console. Is this a known issue?

deeplook:test-dask-ec2 dinu$ dask-ec2 up --region-name eu-central-1 --keyname my_aws_key --keypair ~/.ssh/my_aws_key.pem --ami ami-ac1524b1
[...]

deeplook:test-dask-ec2 dinu$ dask-ec2 destroy
Are you sure you want to destroy the cluster? [y/N]: y
DEBUG: Searching for default VPC
DEBUG: Default VPC found - Using VPC ID: vpc-d63fe9b3
DEBUG: Searching for default subnet in VPC vpc-d63fe9b3
DEBUG: Default subnet found - Using Subnet ID: subnet-5fa49277
Terminating instances
DEBUG: Terminating instances: ['i-b7f06f0a', 'i-adf06f10', 'i-acf06f11', 'i-aff06f12']
Unexpected EC2 error: An error occurred (InvalidInstanceID.NotFound) when calling the DescribeInstances operation: The instance IDs 'i-acf06f11, i-adf06f10, i-aff06f12, i-b7f06f0a' do not exist

deeplook:test-dask-ec2 dinu$ dask-ec2 --version
dask-ec2, version v0.3.0+8.gc9da588
danielfrg commented 8 years ago

Thanks for the report. I think this is because you changed the default region on up but we don't have the same flag on destroy, we should do that and/or save that info in the cluster.yaml.

deeplook commented 8 years ago

@danielfrg Sounds reasonable.