Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 7 Mar 2017 10:42:38 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13031147.1483041435000.237.1488883358088@Atlassian.JIRA>
In-Reply-To: <JIRA.13031147.1483041435000@Atlassian.JIRA>
References: <JIRA.13031147.1483041435000@Atlassian.JIRA> <JIRA.13031147.1483041435903@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9719) [VMware] VR loses DHCP
 settings and VMs cannot obtain IP after HA recovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 07 Mar 2017 10:42:45 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899207#comment-15899207 ] 

ASF GitHub Bot commented on CLOUDSTACK-9719:
--------------------------------------------

Github user nvazquez commented on the issue:

    https://github.com/apache/cloudstack/pull/1879
  
    @sureshanaparti sure, we use version 6.0.0, build 3634794


> [VMware] VR loses DHCP settings and VMs cannot obtain IP after HA recovery
> --------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9719
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9719
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>            Reporter: Suresh Kumar Anaparti
>            Assignee: Suresh Kumar Anaparti
>             Fix For: 4.10.0.0
>
>
> After HA being triggered on VMware, some VMs fail to acquire DHCP address from a VR. These VMs are live migrated as part of vCenter HA to another available host before the VR and couldn't acquire DHCP address as VR is not migrated yet and these VMs request failed to reach the VR.
> Resolving this requires manual intervention by the CloudStack administrator; the router must be rebooted or the network restarted. This behavior is not ideal and will prolong downtime caused by an HA event and there is no point for the non-functional virtual router to even be running. CloudStack should handle this situation by setting VR restart priority to high in the vCenter when HA is enabled.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)