cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9719) [VMware] VR loses DHCP settings and VMs cannot obtain IP after HA recovery
Date Sat, 22 Apr 2017 15:44:04 GMT

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

ASF subversion and git services commented on CLOUDSTACK-9719:
-------------------------------------------------------------

Commit bf77c07797518bfd8dd05836fced25615f1d8375 in cloudstack's branch refs/heads/4.9 from
[~sureshkumar.anaparti]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=bf77c07 ]

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.15#6346)

Mime
View raw message