Bamboo OnDemand random Client.InvalidZone.NotFound error

I have a custom AMI in the Sydney which I created based on the Bamboo stock image.

I can start a micro instance of this AMI from bamboo and attach an EBS volume from a snapshot.

I can start an m3.medium instane of this AMI from bamboo without attching the EBS volume.

Starting an m3.medium instance of the same AMI attaching the EBS volume doesn't work consistently. It was working this morning. Tonight I get

Creating EBS volume...

Found snapshotId at /root/snapshotId. Snapshot will be restored to /mnt/bamboo-ebs

Cannot find value for 'aws.ebs.deleteOnTermination'. Nothing is written.

mountLocation: /mnt/bamboo-ebs

attachedDeviceLocation: /dev/sdh

instanceId: i-02562d3d

amiId: ami-952db5af

availabilityZone: ap-southeast-2b

Thu Apr 24 11:31:26 UTC 2014

Using snapshotId snap-759bff41

Restoring volume from snap-759bff41...

Client.InvalidZone.NotFound: The zone 'ap-southeast-2b' does not exist.

ec2-create-volume failed (exit code 0). Output:

I have modified the .bash_profile of the root account in the AMI to do

export EC2_URL=https://ec2.ap-southeast-2.amazonaws.com

After doing that it all started working. Until now when it is failing again for no apparent reason.

-----------------------

As I finish writing this post I try to start the m3.medium instance again and it is working again.

So it seems that I am randomly getting this Client.InvalidZone.NotFound error.

Thanks for any help

Lionel.

1 answer

1 accepted

Accepted Answer
0 votes

Is it a recent stock image? Are you creating new image configurations for your tests or is it always the same configuration?

Try the following: start an instance from an image configuration without an EBS, then add the EBS to that configuration and start it again. It should work from then on.

I copied ami-270b444e (3.0-SNAPSHOT-bamboo-snapshot-amzn-ami-pv-2013.03.1.x86_64-ebs-1372107828-BDM-1372609769-BDM1378218549) from us-east-1.

What you suggest is what I had done and perhaps that is why it is working again. But why would starting it without an EBS first fix it? Will it happen again? I think it's already happen twice.


When you start it without an EBS, the agent starts and reports back the image version - only then Bamboo knows that it should start EBSes, by default it expect the image to do it. We are aware that this is a problem.

It should not happen again, unless there's a bug somewhere.

Ok I'll keep an eye on it to see if it happens again. Is there a JIRA issue for this?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

335 views 0 8
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you