You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kelven Yang (JIRA)" <ji...@apache.org> on 2014/05/07 01:30:22 UTC

[jira] [Resolved] (CLOUDSTACK-4639) status of VM is not synced properly when host is HA during hypervisor failure

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

Kelven Yang resolved CLOUDSTACK-4639.
-------------------------------------

    Resolution: Fixed

This is the fixed after internal fixes have been merged into Apache repo

> status of VM is not synced properly when host is HA  during hypervisor failure
> ------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4639
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4639
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.2.1
>         Environment: I have two EXI5.1 host in a cluster having both DRS fully automated and HA enabled . Vmotion was enabled as host level
>            Reporter: shweta agarwal
>            Assignee: Kelven Yang
>            Priority: Critical
>             Fix For: 4.4.0
>
>
> Repro steps:
> Create a vmware cluster environment with both DRS and HA enable
> 1. Create a VM 
> 2. Bring down the hypervisor hosting this VM  by power off
> 3. Wait for VM to HA to other available host .
> 4. Wait for sync interval ( sync.interval	Cluster Delta sync interval in seconds)
> Bug:
> Even after waiting for long  . VM is shown as stopped in CP though they are actually running  and can be accessed via vcenter.



--
This message was sent by Atlassian JIRA
(v6.2#6252)