[
https://issues.apache.org/jira/browse/CLOUDSTACK-10168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16298095#comment-16298095
]
ASF GitHub Bot commented on CLOUDSTACK-10168:
---------------------------------------------
blueorangutan commented on issue #2366: CLOUDSTACK-10168 - VR duplicate entries
in /etc/hosts when reusing VM name
URL: https://github.com/apache/cloudstack/pull/2366#issuecomment-353000660
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been
kicked to run smoke tests
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> VR duplicate entries in /etc/hosts when reusing VM name
> -------------------------------------------------------
>
> Key: CLOUDSTACK-10168
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10168
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.10.0.0, 4.9.2.0, 4.9.1.0, 4.9.0.1, 4.9.3.0
> Environment: * ACS4.9.0.1 + ACS4.9.1 + ACS4.9.2 + ACS4.9.3 +
> ACS4.10.0 / CentOS7
> * KVM / ACS 4.9.1-4.9.2-4.9.3+4.10.0 / CentOS7
> * Isolated networks
> Reporter: Dag Sonstebo
> Assignee: Rohit Yadav
>
> Steps to recreate:
> * Create VM on isolated network.
> * Delete the VM
> * Create a new VM with same name.
> * Repeat this multiple times.
> Result:
> * DNS entries are not housekept, allowing for multiples.
> * DNSmasq name resolution also returns multiple entries.
> * /etc/hosts:
> {code}
> root@r-15-VM:~# cat /etc/hosts
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> 10.1.1.230 R4VM1
> 10.1.1.208 R4VM2
> ::1 localhost ip6-localhost ip6-loopback
> 10.1.1.166 R4VM2
> 10.1.1.1 r-15-VM data-server
> 10.1.1.24 R4VM2
> 10.1.1.221 R4VM2
> 127.0.0.1 localhost r-15-VM
> {code}
> * Name resolving the R4VM2 name:
> {code}
> [root@R4VM1 ~]# nslookup r4vm2
> Server: 10.1.1.1
> Address: 10.1.1.1#53
>
> Name: r4vm2.cs2cloud.internal
> Address: 10.1.1.221
> Name: r4vm2.cs2cloud.internal
> Address: 10.1.1.208
> Name: r4vm2.cs2cloud.internal
> Address: 10.1.1.166
> Name: r4vm2.cs2cloud.internal
> Address: 10.1.1.24
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
