cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4014) Attach volume on a vm deployed with startvm=False fails
Date Thu, 01 Aug 2013 16:09:49 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Prasanna Santhanam updated CLOUDSTACK-4014:
-------------------------------------------

    Fix Version/s: 4.2.0
    
> Attach volume on a vm deployed with startvm=False fails
> -------------------------------------------------------
>
>                 Key: CLOUDSTACK-4014
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4014
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.2.0
>            Reporter: Prasanna Santhanam
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: attchvolumeTostoppedVm.log
>
>
> CloudStack's startVM=false in deployVirtualMachine api allows creating VMs in
> stopped state. When I deploy such a VM and attach a volume to it, I see a
> failure with the stacktrace
> This is from an automated test so I think the test case is valid.
> 2013-08-01 21:34:38,579 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-7:job-33
= [ 5e3f9391-d19e-48f7-b7ad-acb5939be5e1 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
> com.cloud.utils.exception.CloudRuntimeException: Unable to find storage pool when create
volumeDataDisk
>         at com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:676)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1522)
>         at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1820)
>         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:439)
>         at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>         at java.lang.Thread.run(Thread.java:680)
> Attaching managemnt server logs from running on xenserver-devcloud

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message