Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 10 Feb 2014 19:06:23 +0000 (UTC)
From: "Nux (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12694167.1391971558968.18421.1392059183430@arcas>
In-Reply-To: <JIRA.12694167.1391971558968@arcas>
References: <JIRA.12694167.1391971558968@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-6065) No HA for shutdown VM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nux updated CLOUDSTACK-6065:
----------------------------

    Priority: Critical  (was: Major)

> No HA for shutdown VM
> ---------------------
>
>                 Key: CLOUDSTACK-6065
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6065
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, UI
>    Affects Versions: 4.3.0
>         Environment: CentOS 6.5 Mgmt & HVs, KVM
>            Reporter: Nux
>            Priority: Critical
>              Labels: ha, kvm
>
> I create a service offering with HA, launch a VM with it. 
> I stop the VM from its console or SSH by issuing `poweroff` and the VM is not started back on.
> This is what I see in the management log:
> http://fpaste.org/75667/67633139/raw/
> The UI keeps showing this VM as Running.
> However, if I force a reboot of its hypervisor ACS does do the right thing and starts the VM on another HV.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)