cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9719) [VMware] VR loses DHCP settings and VMs cannot obtain IP after HA recovery
Date Fri, 30 Dec 2016 06:01:58 GMT


ASF GitHub Bot commented on CLOUDSTACK-9719:

Github user blueorangutan commented on the issue:
    @karuturi I understand these words: "help", "hello", "thanks", "package", "test"
    Test command usage: test [mgmt os] [hypervisor] [additional tests]
    Mgmt OS options: ['centos6', 'centos7', 'ubuntu']
    Hypervisor options: ['kvm-centos6', 'kvm-centos7', 'kvm-ubuntu', 'xenserver-65sp1', 'xenserver-62sp1',
'vmware-60u2', 'vmware-55u3', 'vmware-51u1', 'vmware-50u1']
    Additional tests: list of comma separated tests with paths relative to the `test/integration`
directory, for example: component/, component/
    Note: when additional tests are passed, you need to specify mgmt server os and hypervisor
or use the `matrix` command.
    Blessed contributors for kicking Trillian test jobs: ['rhtyd', 'jburwell', 'murali-reddy',
'abhinandanprateek', 'PaulAngus', 'borisstoyanov', 'karuturi']

> [VMware] VR loses DHCP settings and VMs cannot obtain IP after HA recovery
> --------------------------------------------------------------------------
>                 Key: CLOUDSTACK-9719
>                 URL:
>             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:
> 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

View raw message