Issue Summary

Elastic instances are incorrectly marked as 'pending' after several Bamboo restart attempts

This is reproducible on Data Center: no

Steps to Reproduce

Can't reproduce the issue

Expected Results

Elastic agents should not count as 'pending' once the agent reconnects

Actual Results

The below message is thrown in the atlassian-bamboo.log file:

Deferring new Elastic instance(s) startup. Number of elastic builds in queue threshold Average queue time threshold (-6/1).
There are no agents that can build: TEST-TEST-JOB1-1. New elastic instance(s) will be started (providing the configuration allows it)
1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.

Workaround

You can try one of the 2 workarounds:

1. stop the instances that were created before the Bamboo restart. This should remove them from 'pending instances' list.
2. Add the -Dbamboo.ignore.server.state.on.restart=true system property to Bamboo and restart it. The property should be used only when the issue occurs and removed after the application restart. Warning: This will disable Bamboo's Seemless restarts