Right. The "avoid set" error should be interpreted as "scroll up to
find the real error". It is only a temporary state and indicates there
was a failure earlier in the attempted action. So look at the log more
carefully, or upload it on Pastebin and ask on the list.
Best regards,
Kirk
On 07/24
I'll add onto Prasanna's email by saying avoid set is cleared on each
deploy vm. So if youre seeing that a lot, there's issues elsewhere. Reading
the log line by line when deploying is pretty helpful, you can see what
hosts are available for initial deploy, as well as storage pools. Usually
there i
On Wed, Jul 24, 2013 at 10:34:58AM -0600, Caleb Call wrote:
> When I've seen this (and I've seen it a lot) I usually see that it
> thinks it's missed a ping and so it puts the host in an avoid set.
> I think the "health check" feature in CS needs a lot of work to be
> much more reliable. Sometimes
When I've seen this (and I've seen it a lot) I usually see that it thinks it's
missed a ping and so it puts the host in an avoid set. I think the "health
check" feature in CS needs a lot of work to be much more reliable. Sometimes
if I let the host sit long enough, it will magically (there's n
Dear all,
Good day to you.
>From time to time, CloudStack will put a hypervisor host on avoid set and
not willing to deploy VM on that host.
===
2013-07-24 13:12:34,639 DEBUG [allocator.impl.FirstFitAllocator]
(Job-Executor-2:job-672 FirstFitRoutingAllocator) Host name: hv-kvm-02,
hostId: 28 is
