[jira] [Updated] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool

2013-04-30 Thread Marcus Sorensen (JIRA) 

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

Marcus Sorensen updated CLOUDSTACK-2281:


Priority: Major  (was: Blocker)

> VM fails to deploy due to planner selecting deleted pool
> 
>
> Key: CLOUDSTACK-2281
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
>Reporter: Marcus Sorensen
>Assignee: Prachi Damle
> Fix For: 4.1.0
>
> Attachments: job9908.txt
>
>
> Having trouble tracking this down. Here's what I did:
> Created a 4.1 advanced zone
> added primary storage A
> deployed a template
> deployed vms
> added new primary storages
> migrated VMs from primary storage A to others
> removed initial primary storage A
> try to deploy new vm from template, not working. It looks like the allocator 
> correctly finds and decides to use pool id 204, but somehow deployment is 
> actually attempted on deleted pool 202. See "Returning Deployment 
> Destination" and "DeploymentPlan is provided":
> 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] 
> (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, 
> adding to list: 19
> 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] 
> (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 
> 4 suitable hosts
> 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): 
> (10663,ROOT)
> 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume
> 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable 
> pools
> 2013-04-29 13:25:49,302 DEBUG 
> [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
> Looking for pools in dc: 1  pod:1  cluster:1
> 2013-04-29 13:25:49,304 DEBUG 
> [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
> FirstFitStoragePoolAllocator has 1 pools to check for allocation
> 2013-04-29 13:25:49,304 DEBUG 
> [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
> Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204
> 2013-04-29 13:25:49,304 DEBUG 
> [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
> Is localStorageAllocationNeeded? false
> 2013-04-29 13:25:49,305 DEBUG 
> [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
> Is storage pool shared? true
> 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] 
> (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 
> 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, 
> disable threshold: 0.85
> 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] 
> (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation 
> [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 
> 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85
> 2013-04-29 13:25:49,327 DEBUG 
> [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
> FirstFitStoragePoolAllocator returning 1 suitable storage pools
> 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Trying to find a potenial host and associated 
> storage pools from the suitable host/pool lists for this VM
> 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable 
> storage pool for volume: ROOT
> 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Host: 17 can access pool: 204
> 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and 
> associated storage pools for this VM
> 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Returning Deployment Destination: 
> Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
>  : 
> Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT-->Pool(204))]
> 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with 
> event: StartRequestedvm's original host id: null new host id: null host id 
> before state transition: null
> 2013-04-29 13:25:49,370 DEBUG [cloud.vm.VirtualMachin

[jira] [Updated] (CLOUDSTACK-2281) VM fails to deploy due to planner selecting deleted pool

2013-04-29 Thread Marcus Sorensen (JIRA) 

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

Marcus Sorensen updated CLOUDSTACK-2281:


Attachment: job9908.txt

job 9908

> VM fails to deploy due to planner selecting deleted pool
> 
>
> Key: CLOUDSTACK-2281
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2281
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0
>Reporter: Marcus Sorensen
>Assignee: Prachi Damle
>Priority: Blocker
> Fix For: 4.1.0
>
> Attachments: job9908.txt
>
>
> Having trouble tracking this down. Here's what I did:
> Created a 4.1 advanced zone
> added primary storage A
> deployed a template
> deployed vms
> added new primary storages
> migrated VMs from primary storage A to others
> removed initial primary storage A
> try to deploy new vm from template, not working. It looks like the allocator 
> correctly finds and decides to use pool id 204, but somehow deployment is 
> actually attempted on deleted pool 202. See "Returning Deployment 
> Destination" and "DeploymentPlan is provided":
> 2013-04-29 13:25:49,293 DEBUG [allocator.impl.FirstFitAllocator] 
> (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Found a suitable host, 
> adding to list: 19
> 2013-04-29 13:25:49,294 DEBUG [allocator.impl.FirstFitAllocator] 
> (Job-Executor-10:job-9908 FirstFitRoutingAllocator) Host Allocator returning 
> 4 suitable hosts
> 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Checking suitable pools for volume (Id, Type): 
> (10663,ROOT)
> 2013-04-29 13:25:49,297 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) We need to allocate new storagepool for this volume
> 2013-04-29 13:25:49,299 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Calling StoragePoolAllocators to find suitable 
> pools
> 2013-04-29 13:25:49,302 DEBUG 
> [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
> Looking for pools in dc: 1  pod:1  cluster:1
> 2013-04-29 13:25:49,304 DEBUG 
> [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
> FirstFitStoragePoolAllocator has 1 pools to check for allocation
> 2013-04-29 13:25:49,304 DEBUG 
> [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
> Checking if storage pool is suitable, name: sansrv-row2-rack0 ,poolId: 204
> 2013-04-29 13:25:49,304 DEBUG 
> [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
> Is localStorageAllocationNeeded? false
> 2013-04-29 13:25:49,305 DEBUG 
> [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-10:job-9908) 
> Is storage pool shared? true
> 2013-04-29 13:25:49,309 DEBUG [cloud.storage.StorageManagerImpl] 
> (Job-Executor-10:job-9908) Checking pool 204 for storage, totalSize: 
> 11984676742758, usedBytes: 879609302221, usedPct: 0.07339449541286318, 
> disable threshold: 0.85
> 2013-04-29 13:25:49,327 DEBUG [cloud.storage.StorageManagerImpl] 
> (Job-Executor-10:job-9908) Checking pool: 204 for volume allocation 
> [Vol[10663|vm=6189|ROOT]], maxSize : 11984676742758, totalAllocatedSize : 
> 588879744000, askingSize : 8589934592, allocated disable threshold: 0.85
> 2013-04-29 13:25:49,327 DEBUG 
> [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-10:job-9908) 
> FirstFitStoragePoolAllocator returning 1 suitable storage pools
> 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Trying to find a potenial host and associated 
> storage pools from the suitable host/pool lists for this VM
> 2013-04-29 13:25:49,327 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Checking if host: 17 can access any suitable 
> storage pool for volume: ROOT
> 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Host: 17 can access pool: 204
> 2013-04-29 13:25:49,330 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Found a potential host id: 17 name: ksrv2-000 and 
> associated storage pools for this VM
> 2013-04-29 13:25:49,332 DEBUG [cloud.deploy.FirstFitPlanner] 
> (Job-Executor-10:job-9908) Returning Deployment Destination: 
> Dest[Zone(Id)-Pod(Id)-Cluster(Id)-Host(Id)-Storage(Volume(Id|Type-->Pool(Id))]
>  : 
> Dest[Zone(1)-Pod(1)-Cluster(1)-Host(17)-Storage(Volume(10663|ROOT-->Pool(204))]
> 2013-04-29 13:25:49,370 DEBUG [cloud.capacity.CapacityManagerImpl] 
> (Job-Executor-10:job-9908) VM state transitted from :Stopped to Starting with 
> event: StartRequestedvm's original host id: null new host id: null host id 
> before state transition: null
> 2013-04-