For this instance, you'll need to restart using the old method for launching 
via the console, specifying the zone 1b.  Detection of the zone volumes are in 
for existing clusters and specifying those for launch is on the short list of 
things coming up for cloud launch. 

On Oct 31, 2012, at 10:50 AM, Scooter Willis <hwil...@scripps.edu> wrote:

> Tried it again and same error message. The volume was originally created in 
> us-east-1b and newly created instances are being started in us-east-1a. 
> Shouldn't the availability zone be set to us-east-1b when the instance is 
> requested or that info stored in the properties file in the S3 bucket?
> 
> Any suggestions?
> 
> From: Scooter Willis <hwil...@scripps.edu>
> Date: Wednesday, October 31, 2012 10:32 AM
> To: "galaxy-dev@lists.bx.psu.edu" <galaxy-dev@lists.bx.psu.edu>
> Subject: Amazon
> 
> Started up a cluster on Amazon using the Launch a Galaxy Cloud Instance and 
> got the following message. Since I don't have any control over where the 
> instances are run not sure how I can control this. The last 4 or 5 times I 
> have started up an existing instance has worked with no problem.
> 
> Messages (CRITICAL messages cannot be dismissed.)
> [CRITICAL] Volume 'vol-f882ca85' is located in the wrong availability zone 
> for this instance. You MUST terminate this instance and start a new one in 
> zone 'us-east-1a'. (2012-10-31 14:25:20)
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> 
>  http://lists.bx.psu.edu/
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

  http://lists.bx.psu.edu/

Reply via email to