cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Likitha Shetty (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-4244) Unable to attach a volume to a VM deployed in Stopped (startvm=false) state
Date Mon, 12 Aug 2013 10:38:47 GMT

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

Likitha Shetty resolved CLOUDSTACK-4244.
----------------------------------------

    Resolution: Fixed
    
> Unable to attach a volume to a VM deployed in Stopped (startvm=false) state
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4244
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4244
>             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
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: attachvolume.log.tar.bz2
>
>
> Steps to reproduce:
> 1. Deploy a Virtual Machine in stopped state (startvm=False)
> 2. Create a Volume from any standard disk offering
> 3. attach aforementioned volume to your stopped VM
> Expect:
> Volume attach should be successfull
> Observed:
> Attach volume fails
> 2013-08-12 11:46:50,076 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-7:job-14
= [ 870294b5-d4c8-46c7-9e33-c1142f87364a ]) 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:677)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1538)
>         at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1840)
>         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 management server logs

--
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