Hi, The Host status are:
INIT = 0 MONITORING = 1 MONITORED = 2 ERROR = 3 DISABLED = 4 The CLI shows the MONITORING status as 'on'. The scheduler should use hosts in MONITORED state, instead it is considering all hosts with status < 3. Thanks for the feedback, I've opened a bug [1]. [1] http://dev.opennebula.org/issues/766 -- Carlos Martín, MSc Project Major Contributor OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | cmar...@opennebula.org On Sun, Aug 7, 2011 at 6:03 AM, Rangababu Chakravarthula <rb...@hexagrid.com> wrote: > Using 2.2.1 with KVM. When a host becomes unavailable, opennebula > changes the host status to "err" and when host comes back, it changes > back to "on". However during the period when the host is unavailable, > before every monitoring cycle, the status changes to "on" for a brief > period and goes back to "err". The concern here is during that second, > if a VM request has been made, and that host has been picked as > target, VM provisioning is failing. > Why would the status change to "on" before going back to "err" even > though host is not available? > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org