Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cloudstack.apache.org
Received-SPF: error (nike.apache.org: local policy)
References: 
 <CAM9eXO7BLnY+8HO53xUdQB15Kn-hfdmQuHoKgLeaGE7QEhXDMw@mail.gmail.com>
From: Chip Childers <chip.childers@sungard.com>
In-Reply-To: 
 <CAM9eXO7BLnY+8HO53xUdQB15Kn-hfdmQuHoKgLeaGE7QEhXDMw@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 24 Jul 2013 11:36:35 -0400
Message-ID: <-9186957021600676814@unknownmsgid>
Subject: Re: HA not working - CloudStack 4.1.0 and KVM hypervisor hosts
To: "<users@cloudstack.apache.org>" <users@cloudstack.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

Did you enable HA for your compute offering?

On Jul 24, 2013, at 11:25 AM, Indra Pramana <indra@sg.or.id> wrote:

> Dear all,
>
> I tried to shutdown one of my hypervisor hosts to simulate a server
> failure, and the HA is not working, all the VMs on the affected host is not
> started on another available host.
>
> I am using CloudStack 4.1.0 with KVM hypervisors and Ceph RBD for primary
> storage.
>
> My issue is similar to what is being described here:
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-3535
>
> Except that on my case, the host is indeed marked as "Disconnected" but
> there is no attempt from CloudStack to try starting the VMs on another
> host. I can't provide logs since there's nothing on the logs which suggest
> that CloudStack tries to activate the HA and start the affected VMs on
> another host.
>
> Anyone has similar experience? Anyone knows if the above bug has been
> resolved?
>
> Looking forward to your reply, thank you.
>
> Cheers.