-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Medium
-
Affects Version/s: None
-
Component/s: None
-
None
As of today (Nov 17th), after Bamboo's upgrade to 5.7, users are currently unable to attach EBS volumes to S3 backed AMIs. The following error shows up on the UI:
System Error Details Elastic Bamboo Error : EC2 Instance failed to start: EC2 instance order failed. (com.amazonaws.AmazonServiceException : EBS block device mappings not supported for instance-store AMIs. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 717d6a12-45f8-44d4-8133-a4c69133d42c)) Occurred: 17 Nov 2014, 9:00:00 AM com.amazonaws.AmazonServiceException: EBS block device mappings not supported for instance-store AMIs. (Service: AmazonEC2; Status Code: 400; Error Code: UnsupportedOperation; Request ID: 717d6a12-45f8-44d4-8133-a4c69133d42c) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1053) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:662) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:428) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:290) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225) at com.amazonaws.services.ec2.AmazonEC2Client.runInstances(AmazonEC2Client.java:4382) at com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:129) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:460) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:443) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:103) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
Workaround
Change your Image Configurations to use a EBS backed AMI instead of a S3 backed one.