nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Stock windows image Elastic Agent stuck as 'Pending'

MattD

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

Accepted answers

Ofer Zelig

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/

All comments

Shahriyar Imanov

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.

MattD

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?

Ofer Zelig

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/

MattD

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

Ofer Zelig

Good to know

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo

elastic-agent