You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Likitha Shetty (JIRA)" <ji...@apache.org> on 2014/07/08 08:43:35 UTC

[jira] [Created] (CLOUDSTACK-7077) Quickly attaching multiple data disks to a VM fails

Likitha Shetty created CLOUDSTACK-7077:
------------------------------------------

             Summary: Quickly attaching multiple data disks to a VM fails
                 Key: CLOUDSTACK-7077
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7077
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: VMware, Volumes
    Affects Versions: 4.2.0
            Reporter: Likitha Shetty
            Assignee: Likitha Shetty
             Fix For: 4.5.0


When trying to attach multiple data disks to a VM in quick succession, AttachVolumeCmds consistently fail with the below exception -.

{noformat}
2014-05-19 15:55:18,776 ERROR [storage.resource.VmwareStorageProcessor] (DirectAgent-xxx) AttachVolumeCommand failed due to Exception: java.lang.RuntimeException
Message: Invalid configuration for device '0'.
java.lang.RuntimeException: Invalid configuration for device '0'.
at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:412)
at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.attachDisk(VirtualMachineMO.java:1026)
at com.cloud.storage.resource.VmwareStorageProcessor.attachVolume(VmwareStorageProcessor.java:1281)
at com.cloud.storage.resource.VmwareStorageProcessor.attachVolume(VmwareStorageProcessor.java:1216)
at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java:129)
at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHandlerBase.java:55)
at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:559)
at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-05-19 15:55:18,778 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-151:null) Seq 51-1760168847: Response Received:
2014-05-19 15:55:18,778 DEBUG [agent.transport.Request] (DirectAgent-151:null) Seq 51-1760168847: Processing: { Ans: , MgmtId: 345052289567, via: 51, Ver: v1, Flags: 10, [{"org.apache.cloudstack.storage.command.AttachAnswer":{"result":false,"details":"AttachVolumeCommand failed due to Exception: java.lang.RuntimeException\nMessage: Invalid configuration for device '0'.\n","wait":0}}] }
2014-05-19 15:55:18,778 DEBUG [agent.transport.Request] (Job-Executor-37:job-23717 = [ d261e185-5c78-407e-b3c4-f0d5fcf711df ]) Seq 51-1760168847: Received: { Ans: , MgmtId: 345052289567, via: 51, Ver: v1, Flags: 10,
{ AttachAnswer }
}
2014-05-19 15:55:18,786 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-37:job-23717 = [ d261e185-5c78-407e-b3c4-f0d5fcf711df ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to attach volume: psvgwin28c3pfeng [2] to VM: 37e328e4-c620-48a2-9e35-1fc5225d5a4b; AttachVolumeCommand failed due to Exception: java.lang.RuntimeException
Message: Invalid configuration for device '0'.
at com.cloud.storage.VolumeManagerImpl.sendAttachVolumeCommand(VolumeManagerImpl.java:1712)
at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1944)
at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
2014-05-19 15:55:18,789 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-37:job-23717 = [ d261e185-5c78-407e-b3c4-f0d5fcf711df ]) Complete async job-23717 = [ d261e185-5c78-407e-b3c4-f0d5fcf711df ], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to attach volume: psvgwin28c3pfeng [2] to VM: 37e328e4-c620-48a2-9e35-1fc5225d5a4b; AttachVolumeCommand failed due to Exception: java.lang.RuntimeException
Message: Invalid configuration for device '0'.
{noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)