Low Description
Seen on the manage elastic instances page:
Elastic Bamboo Error : EC2 Instance i-ea9ed400 is in an unrecognised state: UNKNOWN: Failure in EC2 instance i-ea9ed400. Attempting to terminate.
I don't know what it means but it looks like something Bamboo should handle on its own - hence I've filed this bug report.
Details stack trace from the system log entry is:
com.atlassian.aws.AWSException: EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason [] at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.unexpectedStateException(RemoteEC2InstanceImpl.java:360) at com.atlassian.aws.ec2.EC2InstanceState.handleState(EC2InstanceState.java:207) at com.atlassian.aws.ec2.EC2InstanceState.access$100(EC2InstanceState.java:7) at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:75) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:503) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:112) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)
Happened on CBAC this morning (5.7.0 build 5714 - 05 Nov 14)
Attachments
Issue Links
- was cloned as
-
BDEV-6988 Loading...