cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Mehta (JIRA)" <j...@apache.org>
Subject [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
Date Fri, 14 Nov 2014 22:35:34 GMT

     [ 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)

Mime
View raw message