[
https://issues.apache.org/jira/browse/CLOUDSTACK-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan reopened CLOUDSTACK-1141:
---------------------------------------------
Tested with the latest build from network refactor branch.
After network restart , we see that the new router is being created.This router
is assigned a different Ipv6 address.This router has the entries of teh
existing Vms in /etc/dhcphosts.txt entry.
Since the guest Vms still point to the older Ipv6 address , name resolution
between the new Vms fail.
Router:
root@r-32-VM:~# ifconfig
eth0 Link encap:Ethernet HWaddr 06:01:8c:00:00:33
inet6 addr: fc00:3:1370:0:d857:f566:e49c:4688/64 Scope:Global
inet6 addr: fe80::401:8cff:fe00:33/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:113 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21142 (20.6 KiB) TX bytes:1296 (1.2 KiB)
Guest Vm:
sangeetha@ubuntu-123:~$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver fc00:3:1370::2103:a6ac:2c4d:fad4
sangeetha@ubuntu-123:~$
> Ipv6 - After network restart (and reboot router) , we do not see the existing
> vms dnsentries not being programmed in the router.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1141
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1141
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: Latest build from networkrefactor branch.
> Reporter: Sangeetha Hariharan
> Assignee: Sheng Yang
> Fix For: 4.1.0
>
>
> Ipv6 - After network restart , we do not see the existing vms dnsentries not
> being programmed in the router.
> Steps to reproduce the problem:
> Create a Ipv6 network.
> Deploy vms in this network.
> Restart network with clean option.
> After network is restarted successfully , the router does not have any
> existing vm's dnsentries being programmed in the router.
> /etc/dhcphosts.txt is empty.
> We are not able to reach Vms with in the network using their names.
> rebbot router also does not bring back these entries to the router.
--
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: http://www.atlassian.com/software/jira
