cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bharat Kumar (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-3186) Duplicate entries in /etc/hosts file on VR after reboot
Date Mon, 29 Jul 2013 11:41:53 GMT


Bharat Kumar updated CLOUDSTACK-3186:

    Assignee:     (was: Bharat Kumar)
> Duplicate entries in /etc/hosts file on VR after reboot
> -------------------------------------------------------
>                 Key: CLOUDSTACK-3186
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Latest build from master6-17-statble branch
>            Reporter: Sanjeev N
>             Fix For: 4.2.0
> /etc/hosts file on VR contains the IP address to Host Name mappings.
> In 4.2 we have introduced a new entry called "data-server" and mapped to Router VMs eth0
interface ip address. This is for the guest vms  to access user-data and ssh-keys from the
Router VM. 
> Please refer to bug for more info.
> Making this entry in the hosts file is part of cloud-early-config file and every time
a router is rebooted new entry would be made to the hosts file.
> If the router reboots multiple times for some reason, we see lot of duplicate entries
in the hosts file.
> Following is the contents from /etc/hosts file from VR which was rebooted for multiple
>       localhost
> # The following lines are desirable for IPv6 capable hosts
> ::1     localhost ip6-localhost ip6-loopback
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> data-server
> r-4-VM
> data-server
> r-4-VM
> data-server
> r-4-VM
> s1
> s1-passwd
> addaf9b0-bdbc-4c4a-80ed-67664ad781e0
> 3b2804dd-225d-4cf3-bcdc-fed468c61192
> s2
> 0e0df8e6-2c0f-455b-8571-b5f6a0dbd44e
> s2-passwd
> bf2e0e55-a2c9-4d26-a489-b8d8aa596350
> It would be good to check for the entries present in the file before appending to it
and avoid duplicate entries.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message