Return-Path: X-Original-To: apmail-incubator-cloudstack-issues-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3F977D62F for ; Sat, 16 Mar 2013 01:48:13 +0000 (UTC) Received: (qmail 48170 invoked by uid 500); 16 Mar 2013 01:48:12 -0000 Delivered-To: apmail-incubator-cloudstack-issues-archive@incubator.apache.org Received: (qmail 48145 invoked by uid 500); 16 Mar 2013 01:48:12 -0000 Mailing-List: contact cloudstack-issues-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-issues@incubator.apache.org Received: (qmail 48136 invoked by uid 99); 16 Mar 2013 01:48:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Mar 2013 01:48:12 +0000 Date: Sat, 16 Mar 2013 01:48:12 +0000 (UTC) From: "Sangeetha Hariharan (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (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. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-1701: -------------------------------------------- Assignee: Sheng Yang Description: 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 ~]# was: ipv6 - When VM is deployed as part of 2 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 ~]# Summary: 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. (was: ipv6 - When VM is deployed as part of 2 networks , in /ect/resolv.conf domain -name of the non default network is programmed resulting in name resolution failing.) > 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 > Fix For: 4.1.0 > > > 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