com.xerox.amazonws.ec2.EC2Exception

Client error : The volume 'vol-c90ffaa0' is not 'attached'.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web24

  • via Atlassian JIRA by Ulrich Kuhnhardt [Atlassian], 1 year ago
    Client error : The volume 'vol-c90ffaa0' is not 'attached'.
  • via Atlassian JIRA by Ulrich Kuhnhardt [Atlassian], 11 months ago
    Client error : The volume 'vol-c90ffaa0' is not 'attached'.
  • via Atlassian JIRA by Krystian Nowak, 11 months ago
    Client error : The volume 'vol-b48c62dd' is not 'attached'.
  • Stack trace

    • com.xerox.amazonws.ec2.EC2Exception: Client error : The volume 'vol-c90ffaa0' is not 'attached'. at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:1680) at com.xerox.amazonws.ec2.Jec2.detachVolume(Jec2.java:1569) at com.atlassian.aws.ec2.EBSVolumeImpl.delete(EBSVolumeImpl.java:38) at com.atlassian.bamboo.agent.elastic.server.EBSVolumeSupervisorImpl.purge(EBSVolumeSupervisorImpl.java:119) at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl$1.ec2InstanceStateChanged(RemoteElasticInstanceImpl.java:307) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$4.run(RemoteEC2InstanceImpl.java:518) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:98) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.setState(RemoteEC2InstanceImpl.java:513) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.terminated(RemoteEC2InstanceImpl.java:346) at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:125) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:437) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:25) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:127) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:98) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.