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-9583) VR: In CsDhcp.py preseed both hostaname and localhost to resolve to 127.0.0.1
Date Tue, 08 Nov 2016 11:22:58 GMT

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

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

GitHub user murali-reddy opened a pull request:

    https://github.com/apache/cloudstack/pull/1750

    CLOUDSTACK-9583: VR: In CsDhcp.py preseed both hostaname and localhost to resolve to 127.0.0.1

    
    ensuring for both vpc and non vpc vr, both localhost and hostname is resolved to 127.0.0.1

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/murali-reddy/cloudstack vr_dhcp_entries

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1750.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 #1750
    
----
commit 0ac2539dfc50d5502d733aabbaf5fa6148aee4ca
Author: Murali Reddy <muralimmreddy@gmail.com>
Date:   2016-11-08T11:20:41Z

    CLOUDSTACK-9583: VR: In CsDhcp.py preseed both hostaname and localhost to resolve to 127.0.0.1
    
    ensuring for both vpc and non vpc vr, both localhost and hostname is resolved to 127.0.0.1

----


> VR: In CsDhcp.py preseed both hostaname and localhost to resolve to 127.0.0.1
> -----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9583
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9583
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Murali Reddy
>             Fix For: 4.9.1.0
>
>
> It is observed that  'ip route flush' was timing out after 20 seconds with the error
that can't resolve the name of the vrouter. Since this is done for each rule for a router
with a lot of rules, adding the entry to hosts file fixes it and the router provisioning is
observed faster. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message