[ https://issues.apache.org/jira/browse/CLOUDSTACK-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14186050#comment-14186050 ]
ASF subversion and git services commented on CLOUDSTACK-1771: ------------------------------------------------------------- Commit 307a35a618b4e7233368d176ec0e6bbc93aac31b in cloudstack's branch refs/heads/master from [~yasker] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=307a35a ] CLOUDSTACK-1771: Fix VR IP change when restartnetwork with cleanup=true in basic zone In basic network, the correct network id associate with IP is source network id rather than network id. > IPv6 - Network restart for a dual network , results in the ipv4 address of > the router to be changed. After netwpork restart , name resolution of the Vms > fail. > --------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-1771 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1771 > 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, 4.2.0 > Environment: Build from 4.1 > Reporter: Sangeetha Hariharan > Assignee: Sheng Yang > Fix For: 4.2.0 > > > IPv6 - Network restart for a dual network , results in the ipv4 address of > the router to be changed. After netwpork restart , name resolution of the Vms > fail > Steps to reproduce the problem: > Pre Req: > 1.Create Dual Stack Shared Network by passing ipv6 params and ipv4 params > 2. Deploy few Vms in this network. > Steps: > 1. Restart Network. > Expected Behavior: > After network restart , we should be able to access all the Vms within the > network using its name. > Actual Result: > After network restart , we are not able to access all the Vms within the > network using its name. > This is because of the ipv4 address of the router being changed after > network restart. > Router had ip address - 10.223.136.69 > After reboot , Router now has ip address - 10.223.136.69 > But the guest Vms still point to the routers old ipaddress - 10.223.136.69 > for providing name resolution. > sangeetha@test123:~$ 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 10.223.136.69 > nameserver 72.52.126.11 > nameserver 72.52.126.12 > search hello1361 -- This message was sent by Atlassian JIRA (v6.3.4#6332)