[StarCluster] InvalidParameterCombination error with General Purpose SSD AMIs

[MacMullan, Hugh]

A workaround:

diff awsutils.py.devel awsutils.py
509c509
<                              block_device_map=block_device_map,
---
>                              block_device_map=None,
614c614
<             block_device_map=block_device_map,
---
>             block_device_map=None,

No idea what all that stuff does … there still seems to be the correct ephemeral drives attached, and /dev/xvdaa on /mnt, like usual. Hmm.

-Hugh

From: MacMullan, Hugh
Sent: Thursday, September 25, 2014 1:12 PM
To: 'Ying Sonia Ting'
Cc: starcluster at mit.edu
Subject: RE: [StarCluster] InvalidParameterCombination error with General Purpose SSD AMIs

Hi Sonia:

Thanks, yes I understand the workaround (my Magnetic AMIs still work fine) … just wanted to use the SSDs, as they're part of 'normal' EC2 these days. I didn't see the other issue (had searched for SSD instead of gp2) … thanks!

-Hugh

From: Ying Sonia Ting [mailto:sonia810 at uw.edu]
Sent: Thursday, September 25, 2014 12:35 PM
To: MacMullan, Hugh
Cc: starcluster at mit.edu<mailto:starcluster at mit.edu>
Subject: Re: [StarCluster] InvalidParameterCombination error with General Purpose SSD AMIs

Hi,

I'm new to StarCluster but I ran into this bug before.

The AMIs in question in my case were my customized AMIs that I modified (adding tools and such) from the public StarCluster AMI.  What I found is that although the customized AMIs was based on fully-StarCluster-functional AMI with volume type=Magnetic, the instance I used to modify AMIs used gp2 SSD.  My workaround was 1) start an instance with the customized StarCluster-not-functional AMI and specify volume type=Magnetic for that instance. 2) create an AMI from the instance.  The resulting AMI became fully-StarCluster-functional again (at least in my case).

Hope this is helpful and hope that in the near future StarCluster will support gp2 volumes as others have requested here https://github.com/jtriley/StarCluster/issues/264

Cheers,
Sonia



On Thu, Sep 25, 2014 at 8:30 AM, MacMullan, Hugh <hughmac at wharton.upenn.edu<mailto:hughmac at wharton.upenn.edu>> wrote:
Hi StarCluster Community:

I just submitted an 'issue' (https://github.com/jtriley/StarCluster/issues/448), but I thought I would mention this here as well, in case someone has any thoughts.

When using an AMI with volume type = General Purpose (SSD), I get (in debug.log):

2014-09-25 11:08:08,984 PID: 8599 awsutils.py:497 - DEBUG - Forcing delete_on_termination for AMI: ami-083b8e60
2014-09-25 11:08:09,120 PID: 8599 cli.py:277 - ERROR - InvalidParameterCombination: The parameter iops is not supported for gp2 volumes.
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/starcluster/cli.py", line 274, in main
    sc.execute(args)
  File "/usr/lib/python2.6/site-packages/starcluster/commands/start.py", line 244, in execute
    validate_running=validate_running)
  File "/usr/lib/python2.6/site-packages/starcluster/cluster.py", line 1628, in start
    return self._start(create=create, create_only=create_only)
  File "<string>", line 2, in _start
  File "/usr/lib/python2.6/site-packages/starcluster/utils.py", line 112, in wrap_f
    res = func(*arg, **kargs)
  File "/usr/lib/python2.6/site-packages/starcluster/cluster.py", line 1643, in _start
    self.create_cluster()
  File "/usr/lib/python2.6/site-packages/starcluster/cluster.py", line 1163, in create_cluster
    self._create_flat_rate_cluster()
  File "/usr/lib/python2.6/site-packages/starcluster/cluster.py", line 1185, in _create_flat_rate_cluster
    force_flat=True)[0]
  File "/usr/lib/python2.6/site-packages/starcluster/cluster.py", line 966, in create_nodes
    resvs.append(self.ec2.request_instances(image_id, **kwargs))
  File "/usr/lib/python2.6/site-packages/starcluster/awsutils.py", line 525, in request_instances
    **shared_kwargs)
  File "/usr/lib/python2.6/site-packages/starcluster/awsutils.py", line 626, in run_instances
    return self.conn.run_instances(image_id, **kwargs)
  File "/usr/lib/python2.6/site-packages/boto/ec2/connection.py", line 975, in run_instances
    verb='POST')
  File "/usr/lib/python2.6/site-packages/boto/connection.py", line 1188, 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>InvalidParameterCombination</Code><Message>The parameter iops is not supported for gp2 volumes.</Message></Error></Errors><RequestID>c8306558-f673-4fb6-9ea1-64b4d6fdd1c7</RequestID></Response>

The AMIs in question are clones of fully-StarCluster-functional volume type = Magnetic.

Cheers,
-Hugh

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



--
Ying S. Ting
Graduate Student, MacCoss Lab
Department of Genome Sciences, University of Washington

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20140925/628f7c02/attachment-0001.htm