[
https://issues.apache.org/jira/browse/CLOUDSTACK-9719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786083#comment-15786083
]
ASF GitHub Bot commented on CLOUDSTACK-9719:
--------------------------------------------
GitHub user sureshanaparti opened a pull request:
https://github.com/apache/cloudstack/pull/1879
CLOUDSTACK-9719: [VMware] VR loses DHCP settings and VMs cannot obtain IP
after HA recovery - Set high restart priority for the VR.
[VMware] VR loses DHCP settings and VMs cannot obtain IP after HA recovery.
Fix: Set high restart priority for the VR.
Test scenarios:
- Enable cluster HA after VR is created. Now stop and start VR and check
its restart priority, should be High.
- Enable cluster HA before VR is created. Now create some VM and verify
that VR created must have High restart priority.
Issue validation steps:
- Create a VMware setup with a cluster having 2 ESXi hosts and Enable HA at
cluster level in vCenter.
- Creat a Network offering with DHCP and source NAT
- Create few VMs using network created above and Ensure that router VM is
created with restart priority set to High.
- Make the ESXi host (where router VM is running) unreachable.
- Verified that router VM is first migrated to other host and VMs acquire
IP via DHCP.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack CLOUDSTACK-9719
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1879.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1879
----
commit afa642974b19c35bd60c5271b1388c0958a0a653
Author: Suresh Kumar Anaparti <suresh.anapa...@accelerite.com>
Date: 2016-12-29T20:27:02Z
CLOUDSTACK-9719: [VMware] VR loses DHCP settings and VMs cannot obtain IP
after HA recovery - Set high restart priority for the VR.
Test scenarios:
- Enable cluster HA after VR is created. Now stop and start VR and check
its restart priority, should be High.
- Enable cluster HA before VR is created. Now create some VM and verify
that VR created must have High restart priority.
----
> [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.4#6332)
