You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rajani Karuturi (JIRA)" <ji...@apache.org> on 2015/03/16 04:43:42 UTC

[jira] [Updated] (CLOUDSTACK-8255) Add secondary IP to correct ethernet interface present on the VM

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

Rajani Karuturi updated CLOUDSTACK-8255:
----------------------------------------
    Fix Version/s:     (was: 4.5.0)
                   4.5.1

> 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.1
>
>
> 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)