[ https://issues.apache.org/jira/browse/CLOUDSTACK-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Animesh Chaturvedi updated CLOUDSTACK-4432: ------------------------------------------- Tagging for 4.2.1 > [VMWare] NPE thrown during VM Deployment > ---------------------------------------- > > Key: CLOUDSTACK-4432 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4432 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: VMware > Affects Versions: 4.2.0 > Reporter: Chandan Purushothama > Priority: Critical > Fix For: 4.2.1 > > Attachments: management-server.zip > > > =========== > Observation: > =========== > 2013-08-21 17:09:32,344 DEBUG [allocator.impl.FirstFitAllocator] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ] > FirstFitRoutingAllocator) Found a suitable host, adding to list: 10 > 2013-08-21 17:09:32,345 DEBUG [allocator.impl.FirstFitAllocator] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ] > FirstFitRoutingAllocator) Host Allocator returning 1 suitable hosts > 2013-08-21 17:09:32,346 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) Checking > suitable pools for volume (Id, Type): (18,ROOT) > 2013-08-21 17:09:32,346 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) We need > to allocate new storagepool for this volume > 2013-08-21 17:09:32,347 DEBUG [cloud.deploy.DeploymentPlanningManagerImpl] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) Calling > StoragePoolAllocators to find suitable pools > 2013-08-21 17:09:32,349 DEBUG [storage.allocator.LocalStoragePoolAllocator] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) > LocalStoragePoolAllocator trying to find storage pool to fit the vm > 2013-08-21 17:09:32,349 DEBUG > [storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-49:job-66 > = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) ClusterScopeStoragePoolAllocator > looking for storage pool > 2013-08-21 17:09:32,349 DEBUG > [storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-49:job-66 > = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) Looking for pools in dc: 1 pod:1 > cluster:6 > 2013-08-21 17:09:32,350 DEBUG > [storage.allocator.ClusterScopeStoragePoolAllocator] (Job-Executor-49:job-66 > = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) No storage pools available for > shared volume allocation, returning > 2013-08-21 17:09:32,350 DEBUG > [storage.allocator.ZoneWideStoragePoolAllocator] (Job-Executor-49:job-66 = [ > 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) ZoneWideStoragePoolAllocator to find > storage pool > 2013-08-21 17:09:32,353 DEBUG > [storage.allocator.GarbageCollectingStoragePoolAllocator] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) > GarbageCollectingStoragePoolAllocator looking for storage pool > 2013-08-21 17:09:32,361 DEBUG [cloud.storage.StorageManagerImpl] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) Storage > pool garbage collector found 0 templates to clean up in storage pool: > vmware-primary-1 > 2013-08-21 17:09:32,365 DEBUG [cloud.storage.StorageManagerImpl] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) Storage > pool garbage collector found 1 templates to clean up in storage pool: > vmware-primary-2 > 2013-08-21 17:09:32,366 DEBUG [cloud.template.TemplateManagerImpl] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) Evicting > TmplPool[5-7-201-1bb6ddc2f6bf3f918ebd7ead6073aae5] > 2013-08-21 17:09:32,368 DEBUG [agent.transport.Request] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) Seq > 5-357960810: Sending { Cmd , MgmtId: 7471666038533, via: 5, Ver: v1, Flags: > 100111, > [{"com.cloud.agent.api.storage.DestroyCommand":{"volume":{"id":5,"mountPoint":"/export/home/chandan/307PB-195-103/primary2","path":"1bb6ddc2f6bf3f918ebd7ead6073aae5","size":0,"storagePoolType":"NetworkFilesystem","storagePoolUuid":"96bc10ee-70b3-3d20-a60c-c068a024b3a7","deviceId":0},"wait":0}}] > } > 2013-08-21 17:09:32,369 DEBUG [agent.transport.Request] > (Job-Executor-49:job-66 = [ 50b09c49-f155-4b59-b6a3-9c77394fe172 ]) Seq > 5-357960810: Executing: { Cmd , MgmtId: 7471666038533, via: 5, Ver: v1, > Flags: 100111, > [{"com.cloud.agent.api.storage.DestroyCommand":{"volume":{"id":5,"mountPoint":"/export/home/chandan/307PB-195-103/primary2","path":"1bb6ddc2f6bf3f918ebd7ead6073aae5","size":0,"storagePoolType":"NetworkFilesystem","storagePoolUuid":"96bc10ee-70b3-3d20-a60c-c068a024b3a7","deviceId":0},"wait":0}}] > } > 2013-08-21 17:09:32,369 DEBUG [agent.manager.DirectAgentAttache] > (DirectAgent-302:null) Seq 5-357960810: Executing request > 2013-08-21 17:09:32,369 WARN [agent.manager.DirectAgentAttache] > (DirectAgent-302:null) Seq 5-357960810: Exception caught > java.lang.NullPointerException > at > com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:195) > 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) > 2013-08-21 17:09:35,105 DEBUG [agent.manager.AgentManagerImpl] > (AgentManager-Handler-8:null) SeqA 7-11405: Processing Seq 7-11405: { Cmd , > MgmtId: -1, via: 7, Ver: v1, Flags: 11, > [{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":9,"_loadInfo":"{\n > \"connections\": []\n}","wait":0}}] } -- 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