[
https://issues.apache.org/jira/browse/CLOUDSTACK-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911390#comment-13911390
]
Koushik Das commented on CLOUDSTACK-5075:
-----------------------------------------
Didn't see the issue in 4.3 branch. From the logs doesn't look related to KVM.
Tried the following:
1. Deployed a vm on cluster wide storage
2. Created a data volume on local storage
3. Attached it to the vm in step 1
4. Destroyed the vm
Vm got destroyed without getting any warnings in logs.
> issue with destroy vm with local storage ; Unable to update vm disk
> statistics for vm: 42 from host: 1 java.lang.IndexOutOfBoundsException:
> Index: 0, Size: 0
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5075
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5075
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: KVM, Storage Controller
> Affects Versions: 4.2.1
> Reporter: prashant kumar mishra
> Assignee: Koushik Das
> Fix For: 4.3.0
>
> Attachments: Logs_Db.rar
>
>
> Steps to reproduce
> ---------------------------
> 1-Prepare a CS with kvm hypervisor
> 2-deploy a vm either in cluster wide or in zone wide PS
> 3-create a data volume on local storage
> 4-Attache it to vm
> 5-try to destroy vm
> Expected
> ----------
> vm should get destroyed
> Actual
> ---------
> vms are getting destroyed with warnings in logs
> Logs
> ---------
> 2013-11-07 12:51:17,432 DEBUG [agent.manager.AgentManagerImpl]
> (Job-Executor-75:job-197 = [ b73a5588-48f3-445e-b5e0-f39e54d18293 ]) Details
> from executing class com.cloud.agent.api.GetVmDiskStatsCommand:
> 2013-11-07 12:51:17,439 DEBUG [db.Transaction.Transaction]
> (Job-Executor-75:job-197 = [ b73a5588-48f3-445e-b5e0-f39e54d18293 ]) Rolling
> back the transaction: Time = 7 Name =
> -AsyncJobManagerImpl$1.run:494-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRun:334-FutureTask.run:166-ThreadPoolExecutor.runWorker:1110-ThreadPoolExecutor$Worker.run:603-Thread.run:679;
> called by
> -Transaction.rollback:897-UserVmManagerImpl.collectVmDiskStatistics:3632-UserVmManagerImpl.prepareStop:5034-VirtualMachineManagerImpl.advanceStop:1258-VirtualMachineManagerImpl.destroy:1402-VMEntityManagerImpl.destroyVirtualMachine:259-VirtualMachineEntityImpl.destroy:225-UserVmManagerImpl.destroyVm:3484-UserVmManagerImpl.destroyVm:2005-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-DestroyVMCmd.execute:112-ApiDispatcher.dispatch:158
> 2013-11-07 12:51:17,443 WARN [cloud.vm.UserVmManagerImpl]
> (Job-Executor-75:job-197 = [ b73a5588-48f3-445e-b5e0-f39e54d18293 ]) Unable
> to update vm disk statistics for vm: 48 from host: 1
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
> at java.util.ArrayList.rangeCheck(ArrayList.java:571)
> at java.util.ArrayList.get(ArrayList.java:349)
> at
> com.cloud.vm.UserVmManagerImpl.collectVmDiskStatistics(UserVmManagerImpl.java:3557)
> at
> com.cloud.vm.UserVmManagerImpl.prepareStop(UserVmManagerImpl.java:5034)
> at
> com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1258)
> at
> com.cloud.vm.VirtualMachineManagerImpl.destroy(VirtualMachineManagerImpl.java:1402)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.destroyVirtualMachine(VMEntityManagerImpl.java:259)
> at
> org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.destroy(VirtualMachineEntityImpl.java:225)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:3484)
> at
> com.cloud.vm.UserVmManagerImpl.destroyVm(UserVmManagerImpl.java:2005)
> at
> com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at
> org.apache.cloudstack.api.command.user.vm.DestroyVMCmd.execute(DestroyVMCmd.java:112)
> 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)
> 2013-11-07 12:51:17,448 DEBUG [agent.transport.Request]
> (Job-Executor-75:job-197 = [ b73a5588-48f3-445e-b5e0-f39e54d18293 ]) Seq
> 1-1089012365: Sending { Cmd , MgmtId: 6959054979131, via: 1, Ver: v1, Flags:
> 100011,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-48-VM","wait":0}}]
> }
> 2013-11-07 12:51:17,476 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
> ===START=== 10.252.192.57 -- GET
> command=queryAsyncJobResult&jobId=fd0040b2-587f-42ec-84fa-4b07501e777d&response=json&sessionkey=6KOLGCqvy2xe7ijK7YbIxRzcZww%3D&_=1383827262421
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
