Bamboo: Failed to start elastic instances: Error when starting a new instance

I can't start elastic default instance

image2015-7-6 13:22:11.png

image2015-7-6 13:22:24.png

 

EC2 user with "AdministratorAccess". 

 

Any help is much appreciated

Thanks,

Artsiom

7 answers

Hi @Jaime Silveira

I am having the same problem as described by @Artyom Shimanovsky, @christian vejrich and @Reza Farshi.

I am using an Amazon free tier account on a Bamboo Cloud trial version trying to build a .NET application using Elastic Bamboo instance type ami-22a6a33f (Bamboo Windows image with .NET 4.0) which I am not able to start from Bamboo Cloud interface.

Solved it by giving "AmazonEC2FullAccess" to the Elastic Bamboo user in IAM Management Console.

For that you go to Security credentials>Users>ElasticBamboo User>Permissions>Attach Policy>AmazonEC2FullAccess

Would be great if this could be better documented in the Bamboo howto pages for the future.

Best regards,

Vlad

This worked for me. The documentation for Bamboo is really pathetic. I am struggling to create one sample build from few days.

Thank you! This got me running after much frustration!

Thanks, that helped me!

Failed to start elastic instances: Error when starting a new instance

I have the same error.

And no, i can not check the logs im using your cloud service, and that is the only error message you provide. thanks for a horrible user experience.  

Hi Christian. I recommend you setup aws tools (example for linux) and try launch of bamboo instance with this tools (with default bamboo ami, bamboo security group, bamboo pair of keys). You will get full logs of error. I can help you setup this tools, if need

Please can you provide an example of this, we are on trial of Bamboo.

Hi Jaime 

I have the same problem. I set access key of root account of AWS in elastic bamboo configuration. also I am able to spin up an instance of ami-b69dd0de  AMI. which is a bamboo AMI. but when I want to start to instance from the bamboo administration panel this error pop up immediately :

Failed to start elastic instances: Error when starting a new instance

So It can not belong to AWS accoutn configuration. 
I am using AWS free tier account , and I am using bamboo 7 day trial version.
Any help appreciated.
Regards Reza

 

Jul 6, 2015 4:41:40 AM Currently there are no agents that can build: ES-DEV-JOB1. New elastic instance(s) will be started (providing the configuration allows it).
Jul 6, 2015 4:41:40 AM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.
Jul 6, 2015 4:42:40 AM Currently there are no agents that can build: ES-DEV-JOB1. New elastic instance(s) will be started (providing the configuration allows it).
Jul 6, 2015 4:42:40 AM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.
Jul 6, 2015 4:43:40 AM Currently there are no agents that can build: ES-DEV-JOB1. New elastic instance(s) will be started (providing the configuration allows it).
Jul 6, 2015 4:43:40 AM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.

Where is that log from? Please be precise so I can find it in my Bamboo Cloud account.

0 votes

Hi, Artyom.

Have you tried checking or recreating your configuration between Bamboo and Amazon? Does the user connecting them have full permission in Amazon?

Also, check your keys and see if they are correctly generated.

If you still can't figure it out, please open a request at Atlassian Support. We'll be glad to help you out solving this problem.

Kind regards,
Jaime Kirch da Silveira
Atlassian Cloud Support

0 votes

Hi, Ayrtom and Reza.

These errors are very generic and it's had to tell what is wrong just by looking at those, as many different problems could say that there was an error starting an instance.

The things I mentioned before (recreating the connection, checking the user has full permission) cover the basics.

If that doesn't solve the problem, further investigation will be necessary, specially checking the logs. For that, you can open a support request at Atlassian Support.

Kind regards,
Jaime Kirch da Silveira
Atlassian Cloud Support

I wasted 4 hours dealing with this bull crap before finding the following unresolved issue:

https://jira.atlassian.com/browse/BAM-16109

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...

453 views 0 9
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