cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-4639) status of VM is not synced properly when host is HA during hypervisor failure
Date Mon, 02 Dec 2013 22:10:36 GMT

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

Alena Prokharchyk reassigned CLOUDSTACK-4639:
---------------------------------------------

    Assignee: Animesh Chaturvedi  (was: Alena Prokharchyk)

Animesh, whoever worked on vmSync feature, should pick it up

> 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: Animesh Chaturvedi
>            Priority: Critical
>             Fix For: 4.3.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.1#6144)

Mime
View raw message