Details
-
Bug
-
Resolution: Fixed
-
Highest
-
None
-
None
-
None
Description
In Bamboo OnDemand you can successfully create an instance of you VPC per the Documentations:
https://confluence.atlassian.com/display/AOD/Elastic+IPs+and+Bamboo
But will be unable to connect. Bamboo is associating an elastic IP (routable). You can ssh to the instance after a delay. The instance will Spinn up and stay in the "Pending" State with the following Error in the logs:
2014-09-29 09:27:13.899585500 2014-09-29 09:27:13,899 INFO [elastic-pool-4-thread-3] [RemoteEC2InstanceImpl] Bamboo has detected that the instance <Instance Name>, previously available at <IP_1> is now available at <IP_2> 2014-09-29 09:27:13.899699500 2014-09-29 09:27:13,899 WARN [elastic-pool-4-thread-3] [RemoteEC2InstanceImpl] The request for the current status of EC2 instance/spot request <Instance Name> failed, try 1. Will retry later. 2014-09-29 09:27:13.899700500 java.lang.NullPointerException 2014-09-29 09:27:13.899701500 at com.atlassian.tunnel.tunnel.client.Tunnel.closeAllTunnels(Tunnel.java:203) 2014-09-29 09:27:13.899701500 at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl$1.onInstanceAddressChange(RemoteElasticInstanceImpl.java:340) 2014-09-29 09:27:13.899708500 at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.handleAddressChange(RemoteEC2InstanceImpl.java:378) 2014-09-29 09:27:13.899709500 at com.atlassian.aws.ec2.EC2InstanceState.handleState(EC2InstanceState.java:193) 2014-09-29 09:27:13.899710500 at com.atlassian.aws.ec2.EC2InstanceState.access$100(EC2InstanceState.java:7) 2014-09-29 09:27:13.899710500 at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:75) 2014-09-29 09:27:13.899711500 at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:512) 2014-09-29 09:27:13.899712500 at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:41) 2014-09-29 09:27:13.899713500 at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:114) 2014-09-29 09:27:13.899716500 at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:85) 2014-09-29 09:27:13.899716500 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) 2014-09-29 09:27:13.899717500 at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) 2014-09-29 09:27:13.899717500 at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) 2014-09-29 09:27:13.899719500 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) 2014-09-29 09:27:13.899719500 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) 2014-09-29 09:27:13.899720500 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) 2014-09-29 09:27:13.899721500 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 2014-09-29 09:27:13.899722500 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 2014-09-29 09:27:13.899723500 at java.lang.Thread.run(Thread.java:662)
Note The ' failed, try 1. Will retry later. ', but Bamboo never tries again and shuts it down about 20 minutes later.
Workaround:
5.7 will have automatic retries built into it, so it should be solved with this. This can be tracked Here still occurring post 5.7
Unfortunately until then the VPC won't work, although manual Elastic IPs associated via This KB , without the use of a VPC should work.