Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 13 Feb 2015 11:53:11 +0000 (UTC)
From: "Gaurav Aradhye (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12774862.1423827020000.38473.1423828391679@Atlassian.JIRA>
In-Reply-To: <JIRA.12774862.1423827020000@Atlassian.JIRA>
References: <JIRA.12774862.1423827020000@Atlassian.JIRA>
 <JIRA.12774862.1423827020294@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-8255) Add secondary IP to correct
 ethernet interface present on the VM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Gaurav Aradhye updated CLOUDSTACK-8255:
---------------------------------------
    Status: Reviewable  (was: In Progress)

> Add secondary IP to correct ethernet interface present on the VM
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8255
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8255
>             Project: CloudStack
>          Issue Type: Test
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.5.0
>            Reporter: Gaurav Aradhye
>            Assignee: Gaurav Aradhye
>              Labels: automation
>             Fix For: 4.5.0
>
>
> In test_lb_secondary_ip.py test cases, secondary ip is added to eth0 interface. However in some of the VMs, this interface is absent and eth2 is present.
> It is wise to list the ethernet interface first, and then use the ethernet interface present on the VM to add the secondary IP to, rather than hard coding the name of the ethernet interface


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)