com.amazonaws.AmazonServiceException: The snapshot ID 'vol-f4a60dec' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSnapshotID.NotFound; Request ID: 6d98e595-e0fc-4d 67-a756-0935492b34a7)

Atlassian JIRA | Bruno Rosa | 2 years ago
  1. 0

    As of today (Nov 17th), after Bamboo's upgrade to 5.7, users are currently unable to start *EC2* instances with an EBS volume attached to them. Even though the EC2 instance has an EBS volume attached, Bamboo keeps searching for a snapshot ID. It fails with the following error message: {noformat} 2014-11-17 15:05:18,884 ERROR [elastic-pool-4-thread-1] [RemoteEC2InstanceImpl] EC2 instance order failed. com.amazonaws.AmazonServiceException: The snapshot ID 'vol-f4a60dec' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSnapshotID.NotFound; Request ID: 6d98e595-e0fc-4d 67-a756-0935492b34a7) 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) at java.lang.Thread.run(Thread.java:662) {noformat} Looking at the error message we can see that it's trying to find a snapshot with ID 'vol-f4a60dec', but this is not a snapshot ID, it's an EBS volume. *Workaround* Create a snapshot from the EBS volume inside AWS and use the snapshot ID in Bamboo while this is not resolved.

    Atlassian JIRA | 2 years ago | Bruno Rosa
    com.amazonaws.AmazonServiceException: The snapshot ID 'vol-f4a60dec' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSnapshotID.NotFound; Request ID: 6d98e595-e0fc-4d 67-a756-0935492b34a7)
  2. 0

    As of today (Nov 17th), after Bamboo's upgrade to 5.7, users are currently unable to start *EC2* instances with an EBS volume attached to them. Even though the EC2 instance has an EBS volume attached, Bamboo keeps searching for a snapshot ID. It fails with the following error message: {noformat} 2014-11-17 15:05:18,884 ERROR [elastic-pool-4-thread-1] [RemoteEC2InstanceImpl] EC2 instance order failed. com.amazonaws.AmazonServiceException: The snapshot ID 'vol-f4a60dec' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSnapshotID.NotFound; Request ID: 6d98e595-e0fc-4d 67-a756-0935492b34a7) 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) at java.lang.Thread.run(Thread.java:662) {noformat} Looking at the error message we can see that it's trying to find a snapshot with ID 'vol-f4a60dec', but this is not a snapshot ID, it's an EBS volume. *Workaround* Create a snapshot from the EBS volume inside AWS and use the snapshot ID in Bamboo while this is not resolved.

    Atlassian JIRA | 2 years ago | Bruno Rosa
    com.amazonaws.AmazonServiceException: The snapshot ID 'vol-f4a60dec' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSnapshotID.NotFound; Request ID: 6d98e595-e0fc-4d 67-a756-0935492b34a7)
  3. 0

    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: {noformat} 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) {noformat} *Workaround* Change your Image Configurations to use a *EBS* backed AMI instead of a S3 backed one.

    Atlassian JIRA | 2 years ago | Marlon Aguiar [Atlassian]
    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)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    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: {noformat} 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) {noformat} *Workaround* Change your Image Configurations to use a *EBS* backed AMI instead of a S3 backed one.

    Atlassian JIRA | 2 years ago | Marlon Aguiar [Atlassian]
    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)
  6. 0

    Provisioning Instance with IAM name and arn returns Error

    GitHub | 9 months ago | nicktylah
    com.amazonaws.AmazonServiceException: The parameter 'iamInstanceProfile.name' may not be used in combination with 'iamInstanceProfile.arn' (Service: AmazonEC2; Status Code: 400; Error Code: InvalidParameterCombination; Request ID: 3162b924-ffed-46b9-9128-a7c87f37864a)

  1. aldrinleal 1 times, last 4 months ago
  2. tyson925 3 times, last 5 months ago
41 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. com.amazonaws.AmazonServiceException

    The snapshot ID 'vol-f4a60dec' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidSnapshotID.NotFound; Request ID: 6d98e595-e0fc-4d 67-a756-0935492b34a7)

    at com.amazonaws.http.AmazonHttpClient.handleErrorResponse()
  2. AWS SDK for Java - Core
    AmazonHttpClient.execute
    1. com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1053)
    2. com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:662)
    3. com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:428)
    4. com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:290)
    4 frames
  3. AWS Java SDK for Amazon EC2
    AmazonEC2Client.runInstances
    1. com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:9225)
    2. com.amazonaws.services.ec2.AmazonEC2Client.runInstances(AmazonEC2Client.java:4382)
    2 frames
  4. com.atlassian.aws
    RemoteEC2InstanceImpl$CatchingRunnableDecorator.run
    1. com.atlassian.aws.ec2.InstanceLauncherFactory$AwsInstanceLauncher.call(InstanceLauncherFactory.java:129)
    2. com.atlassian.aws.ec2.RemoteEC2InstanceImpl.launchInstance(RemoteEC2InstanceImpl.java:460)
    3. com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundStart(RemoteEC2InstanceImpl.java:443)
    4. com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$200(RemoteEC2InstanceImpl.java:39)
    5. com.atlassian.aws.ec2.RemoteEC2InstanceImpl$1.run(RemoteEC2InstanceImpl.java:103)
    6. com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83)
    6 frames
  5. Java RT
    Thread.run
    1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    2. java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
    3. java.util.concurrent.FutureTask.run(FutureTask.java:138)
    4. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
    5. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
    6. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    7. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    8. java.lang.Thread.run(Thread.java:662)
    8 frames