[
https://issues.apache.org/jira/browse/CLOUDSTACK-6065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896879#comment-13896879
]
sadhu suresh commented on CLOUDSTACK-6065:
------------------------------------------
Due to following bug its fail to perform HA
CLOUDSTACK-5713vmsync:KVM:NPE when agentmanager tries to update the
destroyed vm state during vmsync
Also A VM is scheduled for HA when the following conditions occur.
- A host is found to be Down.
- A host is disconnected for more than 30 minutes (time is configurable).
- An agent for a host reports that a VM has stopped running.
- VMs that have been stuck at the Starting state for more than an hour.
- A management server determined that its peer has gone down and is unwinding
any VM that
the peer was trying to start.
- A management server on restart is unwinding any VM that it itself was trying
to start.
> 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
> Assignee: Kelven Yang
> 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)
