Elastic Bamboo Error - Failed on updating stock images

A few weeks ago our build quit working because the custom images needed JDK 1.8.   Fair enough.

Once again the build has quit working and I'm finding another "Elastic Bamboo Error : Failed on updating stock images" error. Occurred: 28 Sep 2015, 2:43:17 AM

From what I've found, the build artifacts are being zipped differently.  I've got screenshots, but i'm getting HTTP errors when I try to insert them here.

We are using a custom windows x86_64 image.  I'm guessing I need to update the image, again.  But update it with what?



java.lang.IllegalArgumentException: Failed on updating stock images ami-963b56fe,ami-963b56fe; expected 0 or 1 stock images for windows - x86_64 - EBS on region US_EAST_1. 
	at com.atlassian.bamboo.agent.elastic.server.ElasticImageConfigurationManagerImpl.updateOrCreateImageData(ElasticImageConfigurationManagerImpl.java:257)
	at com.atlassian.bamboo.agent.elastic.server.ElasticImageConfigurationManagerImpl.updateDefaultElasticImageConfiguration(ElasticImageConfigurationManagerImpl.java:196)
	at com.atlassian.bamboo.container.BambooContainer.start(BambooContainer.java:263)
	at com.atlassian.bamboo.upgrade.UpgradeLauncher.upgradeAndStartBamboo(UpgradeLauncher.java:153)
	at com.atlassian.bamboo.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:41)
	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4704)
	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
	at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
	at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
	at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
	at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
	at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
	at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
	at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
	at org.apache.catalina.core.StandardService.start(StandardService.java:525)
	at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

3 answers

1 accepted

0 vote
Bruno Rosa Atlassian Team Oct 12, 2015

Bill, I tracked it down to a similar problem: BAM-14101. So apparently this issue may be due to a problem on one of Bamboo tables and the error is triggered on every restart of Bamboo. It could have been introduced during an upgrade or a bug that wrote incorrect information on the table. The error can be dismissed and it won't appear until another restart. Since you're running Bamboo Cloud, there is a workaround the support team can perform on your instance at the end of BAM-14101 to get rid of the problem. Please contact support so they can fix this issue for you.

Going to file this as a bug since it's getting no attention here.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn 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,806 views 0 6
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