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

Dominic Blais closed CLOUDSTACK-2388.
-------------------------------------

    Resolution: Fixed
    
> HA "Host Allocator returning 0 suitable hosts" but starting the VM manually 
> finds one.
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2388
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2388
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: KVM
>    Affects Versions: 4.0.2
>         Environment: Ubuntu 12.04.2 amd64 Server on management and compute 
> nodes.
>            Reporter: Dominic Blais
>         Attachments: Management Logs.txt
>
>
> Whenever I try to crash a compute node for the purpose of testing HA 
> respawning of VM on another host, HA-Worker returns  "Host Allocator 
> returning 0 suitable hosts".
> 2013-05-08 09:11:18,179 DEBUG [cloud.deploy.FirstFitPlanner] 
> (HA-Worker-2:work-2) Calling HostAllocators to find suitable hosts
> 2013-05-08 09:11:18,179 DEBUG [allocator.impl.FirstFitAllocator] 
> (HA-Worker-2:work-2 FirstFitRoutingAllocator) Looking for hosts in dc: 1  
> pod:1  cluster:1
> 2013-05-08 09:11:18,181 DEBUG [allocator.impl.FirstFitAllocator] 
> (HA-Worker-2:work-2 FirstFitRoutingAllocator) FirstFitAllocator has 0 hosts 
> to check for allocation: []
> 2013-05-08 09:11:18,183 DEBUG [allocator.impl.FirstFitAllocator] 
> (HA-Worker-2:work-2 FirstFitRoutingAllocator) Found 0 hosts for allocation 
> after prioritization: []
> 2013-05-08 09:11:18,184 DEBUG [allocator.impl.FirstFitAllocator] 
> (HA-Worker-2:work-2 FirstFitRoutingAllocator) Looking for speed=4000Mhz, 
> Ram=4096
> 2013-05-08 09:11:18,184 DEBUG [allocator.impl.FirstFitAllocator] 
> (HA-Worker-2:work-2 FirstFitRoutingAllocator) Host Allocator returning 0 
> suitable hosts
> The thing is, starting the VM manually right after is working because there 
> are plenty enough of ressources.... 

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

Reply via email to