Hi Starcluster Friends!
Just today I heard from a user that he was having trouble adding nodes from the master of a StarCluster created cluster. The AMI is StarCluster public 64-bit Ubuntu EBS non-HVM (ami-765b3e1f in us-east-1). These instances have been working reliably this way for many months, so it seems like something has changed at AWS? Anyone know of anything?
Running default StarCluster 0.95.5
The behavior: locally (not from in EC2) I can add nodes just like normal. From the master, I get this:
$ starcluster an mycluster -a node001
StarCluster - (http://star.mit.edu/cluster
) (v. 0.95.5)
Software Tools for Academics and Researchers (STAR)
Please submit bug reports to starcluster_at_mit.edu
>>> Launching node(s): node001
!!! ERROR - InvalidBlockDeviceMapping: the encrypted flag cannot be specified since device /dev/sda1 has a snapshot specified.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/starcluster/cli.py", line 274, in main
File "/usr/local/lib/python2.7/dist-packages/starcluster/commands/addnode.py", line 128, in execute
File "/usr/local/lib/python2.7/dist-packages/starcluster/cluster.py", line 189, in add_nodes
File "/usr/local/lib/python2.7/dist-packages/starcluster/cluster.py", line 1033, in add_nodes
File "/usr/local/lib/python2.7/dist-packages/starcluster/cluster.py", line 966, in create_nodes
File "/usr/local/lib/python2.7/dist-packages/starcluster/awsutils.py", line 523, in request_instances
File "/usr/local/lib/python2.7/dist-packages/starcluster/awsutils.py", line 624, in run_instances
return self.conn.run_instances(image_id, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py", line 974, in run_instances
File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1204, in get_object
raise self.ResponseError(response.status, response.reason, body)
EC2ResponseError: EC2ResponseError: 400 Bad Request
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error><Code>InvalidBlockDeviceMapping</Code><Message>the encrypted flag cannot be specified since device /dev/sda1 has a snapshot specified.</Message></Error></Errors><RequestID>SOMEREQUESTID</RequestID></Response>
Any thoughts? Anyone else seeing this?
Received on Thu Oct 09 2014 - 15:31:40 EDT