Stock windows image Elastic Agent stuck as 'Pending'

We are currently trialling Bamboo On Demand. Initially, we were able to create a stock windows instance and have an elastic agent run on it.

In the past couple of days, when creating an instance from the 'stock windows instance' image, the elastic agent stays as 'Pending' until the instance eventually terminates itself.

Out of curiosity I started up a stock Ubuntu image and that works fine.

Searching for similar problems has only yielded troubleshooting for custom images... this is happening from the stock windows image.

Any idea what I can do to troubleshoot... or any idea why this is happening?

Cheers

2 answers

1 accepted

It's a fault in Bamboo's default Windows AMI creation.

 

I've provided a solution here: http://fullstack.info/running-bamboo-ci-server-remote-agent-on-windows-server-cloud/

Thanks very much. We ended up moving on from Bamboo due to this issue. It looks like a fine product but we have moved on to appveyor and aren't looking back. Cheers

I'd check AWS EC2 console. If you are using spot requests your bid might be too low and not succeed. Or AWS might be out of Windows based spot instances (generally happens when available Windows license numbers are capped during some rush hours), which means you will have to increase the bid to the amount of OnDemand usage. I recommend checking EC2 console for the AMI of Windows stock image Bamboo uses and launch that same image directly in EC2.

Thanks for your reply. We aren't using spot requests but thanks for thinking about that. I am able to launch the stock AMI directly in EC2. It only shows up as a 'disconnected instance' in Bamboo. As far as comparing the instances side-by-side in EC2, they look the same. I have noticed that when the Bamboo launched instance is running and the agent is pending... RDP into the instance, navigate to the bamboo-elastic-agent directory and try and launch it manually via the .bat script... I get errors about file paths. Manually executing the elastic agent .jar file in the same directory actually 'resolves' the pending status in Bamboo. When I try to run a build however, the build throws errors about trying to find paths within the build directory. When further investigated, the build wasn't copying files into the C:\build\ directory. All that has really told me is that manually executing the .jar file isn't a work around. Is there a way I can try and manually start the elastic agent on the stock instance?

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,499 views 0 5
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