Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@cloudstack.apache.org
Date: Thu, 21 Mar 2013 19:31:16 +0000 (UTC)
From: "Sheng Yang (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12638124.1363825414646.29293.1363894276013@arcas>
In-Reply-To: <JIRA.12638124.1363825414646@arcas>
References: <JIRA.12638124.1363825414646@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-1755) IPv6 - When Vm is part of Dual
 network , /etc/reslov.conf does not have ipv6 router ipaddress and ipv6
 external dns.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sheng Yang updated CLOUDSTACK-1755:
-----------------------------------

    Fix Version/s:     (was: 4.1.0)
                   4.2.0

Move out of 4.1 release.
                
> IPv6 - When Vm is part of Dual network , /etc/reslov.conf does not have ipv6 router ipaddress and ipv6 external dns.
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1755
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1755
>             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: Sheng Yang
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> When Vm is part of Dual network , /etc/reslov.conf does not have ipv6 router ipaddress and ipv6 external dns.
> Steps to reproduce the problem:
> Create a dual network with ipv4 and ipv6 parameters.
> Deploy a Vm in this network.
> On the guest VM , /etc/reslov.conf does not have ipv6 router ipaddress and ipv6 external dns. It has only the ipv4 router ipaddress and ipv4 external dns entries.
> sangeetha@test123:~$ ifconfig
> eth0      Link encap:Ethernet  HWaddr 06:1b:5e:00:00:2a
>           inet addr:10.223.136.67  Bcast:10.223.136.127  Mask:255.255.255
>           inet6 addr: fc00:3:1361:0:3c9e:728f:8582:e4e5/64 Scope:Global
>           inet6 addr: fe80::41b:5eff:fe00:2a/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:113 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:103 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:15767 (15.7 KB)  TX bytes:15206 (15.2 KB)
>           Interrupt:73
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           inet6 addr: ::1/128 Scope:Host
>           UP LOOPBACK RUNNING  MTU:16436  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> 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
> Expected Result:
> On the guest VM , /etc/reslov.conf should have ipv6 router ipaddress and ipv6 external dns entries as well.

--
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