cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9719) [VMware] VR loses DHCP settings and VMs cannot obtain IP after HA recovery
Date Sun, 12 Mar 2017 22:00:05 GMT

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

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

Github user sureshanaparti commented on the issue:

    https://github.com/apache/cloudstack/pull/1879
  
    @nvazquez Thanks for testing the changes. Tested these changes in ESXi 6.0.0, Build 3620759
on vCenter 60U2. I had already looked at the link you provided while fixing this. I observed
the same error on vSphere while testing the changes and fixed this. This is because the VR
instance already exists in the vCenter. Below code fixes that issue:
    
    `clusterDasVmConfigSpec.setOperation(vmAlreadyExists ? ArrayUpdateOperation.EDIT : ArrayUpdateOperation.ADD);
` 


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

Mime
View raw message