You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2013/03/21 20:33:16 UTC

[jira] [Assigned] (CLOUDSTACK-1771) 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.

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheng Yang reassigned CLOUDSTACK-1771:
--------------------------------------

    Assignee: Alena Prokharchyk  (was: Sheng Yang)

I don't know if it's by design or not. In the code router would fine any other ip if the first one in the network is occupied.

Assign to Alena who wrote the allocation code of first ip in network of ipv4.

                
> 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
>         Environment: Build from 4.1
>            Reporter: Sangeetha Hariharan
>            Assignee: Alena Prokharchyk
>            Priority: Critical
>             Fix For: 4.1.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 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