[StarCluster] New Behavior: starcluster addnode error from StarCluster-created master instance

[Justin Riley]

Working on a hotfix 0.95.6 for this now. Stay tuned.

~Justin

On Thu, Oct 09, 2014 at 08:34:30PM +0000, MacMullan, Hugh wrote:
>    Doh! Indeed. That works even better. ;)
> 
>     
> 
>    From: Vasisht Reddy T. [mailto:vasishtreddy at gmail.com]
>    Sent: Thursday, October 09, 2014 4:20 PM
>    To: MacMullan, Hugh
>    Cc: starcluster at mit.edu
>    Subject: Re: [StarCluster] New Behavior: starcluster addnode error from
>    StarCluster-created master instance
> 
>     
> 
>    You might be able to get away with doing a pip install boto==2.32.0 after
>    installing starcluster. 
> 
>    On Thursday, October 9, 2014 at 4:12 PM, MacMullan, Hugh wrote:
> 
>      That is a huge hassle! But it works. ;) I need to rewrite a bunch of
>      scripts (that normally just do `pip install starcluster`). Thanks so
>      much Vasisht.
> 
>       
> 
>      From: Vasisht Reddy T. [[1]mailto:vasishtreddy at gmail.com]
>      Sent: Thursday, October 09, 2014 3:38 PM
>      To: MacMullan, Hugh
>      Cc: [2]starcluster at mit.edu
>      Subject: Re: [StarCluster] New Behavior: starcluster addnode error from
>      StarCluster-created master instance
> 
>       
> 
>      I think it’s an issue with the latest version of boto. Are you using
>      boto-2.33? Downgrading to boto-2.32.0 resolved the issue.
> 
>       
> 
>      Change the boto version in setup.py and reinstall StarCluster
>      (boto==2.32.0)
> 
>       
> 
>       
> 
>      On Thursday, October 9, 2014 at 3:31 PM, MacMullan, Hugh wrote:
> 
>        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 - ([3]http://star.mit.edu/cluster) (v. 0.95.5)
> 
>        Software Tools for Academics and Researchers (STAR)
> 
>        Please submit bug reports to [4]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
> 
>            sc.execute(args)
> 
>          File
>        "/usr/local/lib/python2.7/dist-packages/starcluster/commands/addnode.py",
>        line 128, in execute
> 
>            no_create=self.opts.no_create)
> 
>          File
>        "/usr/local/lib/python2.7/dist-packages/starcluster/cluster.py", line
>        189, in add_nodes
> 
>            no_create=no_create)
> 
>          File
>        "/usr/local/lib/python2.7/dist-packages/starcluster/cluster.py", line
>        1033, in add_nodes
> 
>            spot_bid=spot_bid)
> 
>          File
>        "/usr/local/lib/python2.7/dist-packages/starcluster/cluster.py", line
>        966, in create_nodes
> 
>            resvs.append(self.ec2.request_instances(image_id, **kwargs))
> 
>          File
>        "/usr/local/lib/python2.7/dist-packages/starcluster/awsutils.py", line
>        523, in request_instances
> 
>            **shared_kwargs)
> 
>          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
> 
>            verb='POST')
> 
>          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?
> 
>         
> 
>        -Hugh
> 
>        _______________________________________________
> 
>        StarCluster mailing list
> 
>        [5]StarCluster at mit.edu
> 
>        [6]http://mailman.mit.edu/mailman/listinfo/starcluster
> 
>       
> 
>     
> 
> References
> 
>    Visible links
>    1. mailto:vasishtreddy at gmail.com
>    2. mailto:starcluster at mit.edu
>    3. http://star.mit.edu/cluster
>    4. mailto:starcluster at mit.edu
>    5. mailto:StarCluster at mit.edu
>    6. http://mailman.mit.edu/mailman/listinfo/starcluster

> _______________________________________________
> StarCluster mailing list
> StarCluster at mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
Url : http://mailman.mit.edu/pipermail/starcluster/attachments/20141009/6b52059a/attachment.bin