[
https://issues.apache.org/jira/browse/CLOUDSTACK-9980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071912#comment-16071912
]
ASF subversion and git services commented on CLOUDSTACK-9980:
-------------------------------------------------------------
Commit 3bef90174bec097054911f45cdb77ead493bfb86 in cloudstack's branch
refs/heads/master from [~rajanik]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=3bef901 ]
Merge pull request #2162 from nuagenetworks/vrouter_preformance_fix
CLOUDSTACK-9980: Fix for DNS after network restart with clean up.
> ACS Master: Internal DNS feature breaks on restart network with cleanup
> -----------------------------------------------------------------------
>
> Key: CLOUDSTACK-9980
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9980
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: SystemVM, Virtual Router
> Affects Versions: 4.10.0.0
> Reporter: Mani Prashanth Varma Manthena
> Assignee: Frank Maximus
> Priority: Blocker
> Labels: 4.10.0
> Fix For: 4.10.0.0
>
>
> Steps to reproduce:
> 1) Create an Isolated network with DNS service being provided by VR, and set
> a network domain name.
> 2) Deploy guest VMs in the above created network.
> 3) Verify Internal DNS functionality with the above deployed VMs (e.g.
> hostname --fqdn, ping with hostnames, etc.).
> 4) Restart the network with cleanup, verify that the VR is re-deployed.
> 5) Verify that the Internal DNS functionality is broken.
> {noformat:title=Internal DNS config on VR before restarting the network with
> cleanup}
> root@r-18-VM:~# cat /etc/hosts
> ff02::1 ip6-allnodes
> 10.10.1.1 r-18-VM data-server
> ff02::2 ip6-allrouters
> ::1 localhost ip6-localhost ip6-loopback
> 10.10.1.48 vm02
> 10.10.1.84 vm01
> 127.0.0.1 localhost r-18-VM
> root@r-18-VM:~#
> {noformat}
> {noformat:title=Internal DNS config on VR after restarting the network with
> cleanup}
> root@r-23-VM:~# cat /etc/hosts
> ff02::1 ip6-allnodes
> 10.10.1.1 r-23-VM data-server
> ff02::2 ip6-allrouters
> ::1 localhost ip6-localhost ip6-loopback
> 127.0.0.1 localhost r-23-VM
> root@r-23-VM:~#
> {noformat}
> {noformat:title=Internal DNS functionality on guest VM before restarting the
> network with cleanup}
> [root@vm02 ~]# hostname --fqdn
> vm02.isolated.com
> [root@vm02 ~]#
> [root@vm02 ~]# ping vm01
> PING vm01.isolated.com (10.10.1.84) 56(84) bytes of data.
> 64 bytes from vm01.isolated.com (10.10.1.84): icmp_seq=1 ttl=64 time=2.14 ms
> 64 bytes from vm01.isolated.com (10.10.1.84): icmp_seq=2 ttl=64 time=1.21 ms
> 64 bytes from vm01.isolated.com (10.10.1.84): icmp_seq=3 ttl=64 time=1.36 ms
> 64 bytes from vm01.isolated.com (10.10.1.84): icmp_seq=4 ttl=64 time=1.11 ms
> 64 bytes from vm01.isolated.com (10.10.1.84): icmp_seq=5 ttl=64 time=1.23 ms
> --- vm01.isolated.com ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 3999ms
> rtt min/avg/max/mdev = 1.116/1.413/2.149/0.378 ms
> [root@vm02 ~]#
> {noformat}
> {noformat:title=Internal DNS functionality on guest VM after restarting the
> network with cleanup}
> [root@vm02 ~]# hostname --fqdn
> hostname: Unknown host
> [root@vm02 ~]#
> [root@vm02 ~]# ping vm01
> ping: unknown host vm01
> [root@vm02 ~]#
> {noformat}
> Upon looking at and testing with the latest commits on master, we found out
> that the following commit is causing this issue:
> https://github.com/apache/cloudstack/commit/dab9795bf4dba4fb5aea64933a5099eff0f29c8f
> Work-around: Reverting the above commit
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
