I am launching a brand new instance of the latest AMI. The volume specified in the log does not exist in my account. I was under the impression that the AMI should create this volume for me? 
From: Dannon Baker [dannon.baker@gmail.com]
Sent: Monday, July 22, 2013 4:56 PM
To: Ravpreet Setia
Cc: galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] Cloudman master cannot connect to volume at start-up

Can you verify that the volume does still exist in your account, and that you're launching from the same availability zone that the volume exists in?


On Mon, Jul 22, 2013 at 4:13 PM, Ravpreet Setia <Ravpreet.Setia@oicr.on.ca> wrote:
  • This is what has been reported by the cluster status log: 

  • 20:01:14 - Master starting
  • 20:01:16 - Trouble getting volume reference for volume vol-91cfd1cb: EC2ResponseError: 400 Bad RequestInvalidVolume.NotFoundThe volume 'vol-91cfd1cb' does not exist.9179663c-c5ec-4e90-88ff-ecf606b5e9a6
  • 20:01:16 - Attempting to connect to a non-existent volume vol-91cfd1cb
  • 20:01:16 - Error processing filesystems in existing cluster configuration: 'NoneType' object has no attribute '__getitem__'
  • 20:01:16 - ***** Manager failed to start *****

Any suggestions? 

___________________________________________________________
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/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/