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

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

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

Commit 3b59a9b2e497b6e41cca40cc3147a4cb0a3a52d8 in cloudstack's branch refs/heads/4.9 from
[~rohit.yadav@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3b59a9b ]

Merge pull request #1757 from murali-reddy/vr_dhcp_entries

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

The VR executes a ip route flush command as part of configurations. This command performs
a
DNS lookup on the VR hostname. Since the VR does not have a DNS entry, the ip command would
wait 5 seconds before timing out and executing the flush operation. This fix adds the VR
hostname to /etc/hosts mapped to 127.0.0.1 to answer the DNS lookup  reducing the
execution time.

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

Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>


> 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