You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2013/02/15 01:53:13 UTC
[jira] [Updated] (CLOUDSTACK-1218) IPv6: Shared Network - After
network restart with clean option , router is assigned a different address.
Name resolution for the existing guest Vms in the network fails.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sheng Yang updated CLOUDSTACK-1218:
-----------------------------------
Summary: IPv6: Shared Network - After network restart with clean option , router is assigned a different address. Name resolution for the existing guest Vms in the network fails. (was: Shared Network - After network restart with clean option , router is assigned a different address. Name resolution for the existing guest Vms in the network fails.)
Seems ipv4 would get the first ip in the range whenever possible.
> IPv6: Shared Network - After network restart with clean option , router is assigned a different address. Name resolution for the existing guest Vms in the network fails.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1218
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1218
> 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 network refactor branch.
> Reporter: Sangeetha Hariharan
> Assignee: Sheng Yang
> Fix For: 4.1.0
>
>
> Create a Ipv6 Shared network.
> Deploy few Vms.
> Restart network with clean option.
> After network restart , we see that the new router is being created.This router is assigned a different Ipv6 address (compared to what was assigned to it earlier).
> All the guest Vms still point to the older Ipv6 address for name resolution and hence the name resolution between the 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:~$
--
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