Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 16 Mar 2017 14:01:42 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13031147.1483041435000.37704.1489672902846@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: quoted-printable
archived-at: Thu, 16 Mar 2017 14:01:46 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9719?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D15928094#comment-15928094 ]=20

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

Github user blueorangutan commented on the issue:

    https://github.com/apache/cloudstack/pull/1879
 =20
    Packaging result: =E2=9C=94centos6 =E2=9C=94centos7 =E2=9C=94debian. JI=
D-592


> [VMware] VR loses DHCP settings and VMs cannot obtain IP after HA recover=
y
> -------------------------------------------------------------------------=
-
>
>                 Key: CLOUDSTACK-9719
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-971=
9
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          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 av=
ailable host before the VR and couldn't acquire DHCP address as VR is not m=
igrated yet and these VMs request failed to reach the VR.
> Resolving this requires manual intervention by the CloudStack administrat=
or; 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 p=
oint for the non-functional virtual router to even be running. CloudStack s=
hould handle this situation by setting VR restart priority to high in the v=
Center when HA is enabled.


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