I have changed the instance type of the bamboo image from M1 Old General Purpose Large to T2 Burstable Performance Medium for the image Ubuntu: EBS x86_64 (Ubuntu)
I have created a EBS volume and attached it in the configuration. This causes bamboo to keep failing when trying to start an elastic image.
I get this error, over and over again:
|Jan 16, 2015 9:25:59 AM Currently there are no agents that can build: MYBUILD-JOB1. New elastic instance(s) will be started (providing the configuration allows it).|
|Jan 16, 2015 9:25:59 AM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.|
|Jan 16, 2015 9:25:59 AM Requested that new elastic instance be created for configuration: EBS x86_64 (Ubuntu) / ami-5be8f232|
|Jan 16, 2015 9:25:59 AM Detected that a pending instance request for image [EBS x86_64 (Ubuntu)], ami: ami-5be8f232 has been abandoned.|
Does anyone know how I should go about and debug this?
M3 (medium/large): M3 instances provide better, more consistent performance than M1 instances for most use-cases. M3 instances also offer SSD-backed instance storage that delivers higher I/O performance. M3 instances are also less expensive than M1 instances. Due to these reasons, we recommend M3 for applications that require general purpose instances with a balance of compute, memory, and network resources.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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!
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