cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangeetha Hariharan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1701) ipv6 - When VM is deployed as part of 2 ipv4 networks , in /ect/resolv.conf domain -name of the non default network is programmed resulting in name resolution failing.
Date Thu, 21 Mar 2013 21:03:17 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13609470#comment-13609470
] 

Sangeetha Hariharan commented on CLOUDSTACK-1701:
-------------------------------------------------

Confirmed that this issue does not exist in 4.1.
                
> ipv6 - When VM is deployed as part of 2 ipv4 networks , in /ect/resolv.conf domain -name
of the non default network is programmed resulting in name resolution failing.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-1701
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1701
>             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 network refactor branch.
>            Reporter: Sangeetha Hariharan
>            Assignee: Sheng Yang
>
> ipv6 - When VM is deployed as part of 2 ipv4 networks , in /ect/resolv.conf domain -name
of the non default network is programmed resulting in name resolution failing.
> Steps to reproduce the problem:
> Create a ipv4 network N1 with networkdomain - hello-1373
> Create another ipv4 network N2 with networkdomain - yo-1372
> Deploy a vm , vm1 in N1 (default) and N2.
> Deploy another vm , vm2 in N1.
> From vm1 , trying to reach vm2 by name fails.
> vm1:
> [root@test-dual-vm ~]# ip route
> 10.223.137.128/26 dev eth1  proto kernel  scope link  src 10.223.137.137
> 10.223.137.192/26 dev eth0  proto kernel  scope link  src 10.223.137.195
> 169.254.0.0/16 dev eth1  scope link
> default via 10.223.137.193 dev eth0
> [root@test-dual-vm ~]# cat /etc/resolv.conf
> ; generated by /sbin/dhclient-script
> search yo-1372
> nameserver 10.223.137.194
> [root@test-dual-vm ~]# ssh test-1373-1
> ssh: test-1373-1: Name or service not known
> [root@test-dual-vm ~]#
> vm2:
> [root@test-1373-1 ~]# cat /etc/resolv.conf
> ; generated by /sbin/dhclient-script
> search hello-1373
> nameserver 10.223.137.194
> [root@test-1373-1 ~]# ip route
> 10.223.137.192/26 dev eth0  proto kernel  scope link  src 10.223.137.199
> 169.254.0.0/16 dev eth0  scope link
> default via 10.223.137.193 dev eth0
> [root@test-1373-1 ~]#

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

Mime
View raw message