You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by veera <ve...@cse.iitb.ac.in> on 2014/11/26 17:16:08 UTC
The specified pod is in avoid set, returning
Hi,
I have working cloudstack setup with 1 zone - 1 pod - 2 clusters.
Now I am getting the error "Unable to start a VM due to insufficient
capacity" when i try to start a VM.
the log says "The specified pod is in avoid set, returning".
Any hints?
thanks.
Re: The specified pod is in avoid set, returning
Posted by Kirk Kosinski <ki...@gmail.com>.
Hi, "avoid set" messages indicate some error occurred earlier in the
job, so to find the real error you need to continue looking (i.e. scroll
up in the log). I did this and found:
2014-11-26 16:14:47,834 DEBUG [c.c.a.t.Request]
(AgentManager-Handler-11:null) Seq 33-995164179: Processing: { Ans: ,
MgmtId: 90581290632, via: 33, Ver: v1, Flags: 110,
[{"com.cloud.agent.api.Answer":{"result":false,"details":"ssh: connect
to host 169.254.3.192 port 3922: No route to host","wait":0}}] }
The Virtual Router (r-167-VM) has some kind of problem that is
preventing the host from connecting to it over SSH. You can log into
the VR console to see if you can find why the host cannot reach it on
the NIC with 169.254.3.192, but the fastest solution is probably to just
recreate the VR (assuming there are no other problems in the environment).
There are two ways to recreate a VR.
1) Destroy it in the CloudStack UI or API and start a VM in the network
(such as the affected VM, i-31-168-VM).
2) Restart the network with cleanup enabled, also via the UI or API.
The eventual capacity error is misleading, but it sort of makes sense
when you look at what happened. After the VR problem blocked CloudStack
from starting the VM on the selected host, the pod was put into the
avoid set and CloudStack looked for somewhere else to put the VM. It
could not find capacity elsewhere and thus reports insufficient capacity.
Best regards,
Kirk
On 11/26/2014 08:16 AM, veera wrote:
> Hi,
>
> I have working cloudstack setup with 1 zone - 1 pod - 2 clusters.
> Now I am getting the error "Unable to start a VM due to insufficient
> capacity" when i try to start a VM.
>
> the log says "The specified pod is in avoid set, returning".
> Any hints?
>
> thanks.
Re: The specified pod is in avoid set, returning
Posted by Jayapal Reddy Uradi <ja...@citrix.com>.
Hi Veera,
If you observe the management server logs above the below message will give reason for the failure.
"Unable to start a VM due to insufficient capacity"
Thanks,
Jayapal
On 26-Nov-2014, at 10:25 PM, Tejas Sheth <ts...@gmail.com> wrote:
> Try configuration following parameter in global config.
>
> -> mem.overprovisioning.factor=2
>
> ->cpu.overprovisioning.factor=2
>
> Thanks,
>
> Tejas
>
>
> On Wed, Nov 26, 2014 at 9:54 PM, Andrija Panic <an...@gmail.com>
> wrote:
>
>> Check your network connectivity, if all hosts are UP etc.
>>
>> 2014-11-26 16:14:47,835 INFO [c.c.v.VirtualMachineManagerImpl]
>> (Job-Executor-1:ctx-300e8909 ctx-c12a818e) Unable to contact resource.
>> com.cloud.exception.ResourceUnavailableException: Resource [Pod:1] is
>> unreachable: Unable to apply dhcp entry on router
>>
>> On 26 November 2014 at 17:16, veera <ve...@cse.iitb.ac.in> wrote:
>>
>>> Hi,
>>>
>>> I have working cloudstack setup with 1 zone - 1 pod - 2 clusters.
>>> Now I am getting the error "Unable to start a VM due to insufficient
>>> capacity" when i try to start a VM.
>>>
>>> the log says "The specified pod is in avoid set, returning".
>>> Any hints?
>>>
>>> thanks.
>>
>>
>>
>>
>> --
>>
>> Andrija Panić
>>
Re: The specified pod is in avoid set, returning
Posted by Tejas Sheth <ts...@gmail.com>.
Try configuration following parameter in global config.
-> mem.overprovisioning.factor=2
->cpu.overprovisioning.factor=2
Thanks,
Tejas
On Wed, Nov 26, 2014 at 9:54 PM, Andrija Panic <an...@gmail.com>
wrote:
> Check your network connectivity, if all hosts are UP etc.
>
> 2014-11-26 16:14:47,835 INFO [c.c.v.VirtualMachineManagerImpl]
> (Job-Executor-1:ctx-300e8909 ctx-c12a818e) Unable to contact resource.
> com.cloud.exception.ResourceUnavailableException: Resource [Pod:1] is
> unreachable: Unable to apply dhcp entry on router
>
> On 26 November 2014 at 17:16, veera <ve...@cse.iitb.ac.in> wrote:
>
> > Hi,
> >
> > I have working cloudstack setup with 1 zone - 1 pod - 2 clusters.
> > Now I am getting the error "Unable to start a VM due to insufficient
> > capacity" when i try to start a VM.
> >
> > the log says "The specified pod is in avoid set, returning".
> > Any hints?
> >
> > thanks.
>
>
>
>
> --
>
> Andrija Panić
>
Re: The specified pod is in avoid set, returning
Posted by Andrija Panic <an...@gmail.com>.
Check your network connectivity, if all hosts are UP etc.
2014-11-26 16:14:47,835 INFO [c.c.v.VirtualMachineManagerImpl]
(Job-Executor-1:ctx-300e8909 ctx-c12a818e) Unable to contact resource.
com.cloud.exception.ResourceUnavailableException: Resource [Pod:1] is
unreachable: Unable to apply dhcp entry on router
On 26 November 2014 at 17:16, veera <ve...@cse.iitb.ac.in> wrote:
> Hi,
>
> I have working cloudstack setup with 1 zone - 1 pod - 2 clusters.
> Now I am getting the error "Unable to start a VM due to insufficient
> capacity" when i try to start a VM.
>
> the log says "The specified pod is in avoid set, returning".
> Any hints?
>
> thanks.
--
Andrija Panić