Elastic Bamboo Error - Failed on updating stock images

Bill Langton

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?

Thanks...

 

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)

Bruno Rosa

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.