You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Nitin Mehta (JIRA)" <ji...@apache.org> on 2014/11/14 23:35:34 UTC

[jira] [Updated] (CLOUDSTACK-7919) In vmware, when host crashed and the VR migrated because of HA, Vmsync didnt notice a change in the state and so didnt reprogram the VR

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

Nitin Mehta updated CLOUDSTACK-7919:
------------------------------------
    Summary: In vmware, when host crashed and the VR migrated because of HA, Vmsync didnt notice a change in the state and so didnt reprogram the VR  (was: In vmware, when host crashed and the VR migrated because of HA Vmsync couldnt notice a change in the state (logs pasted above by me) and so didnt reprogram the VR)

> In vmware, when host crashed and the VR migrated because of HA, Vmsync didnt notice a change in the state and so didnt reprogram the VR
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7919
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7919
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.6.0
>            Reporter: Nitin Mehta
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.6.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)