Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 7 Oct 2015 07:31:27 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12901780.1443682191000.43950.1444203087109@Atlassian.JIRA>
In-Reply-To: <JIRA.12901780.1443682191000@Atlassian.JIRA>
References: <JIRA.12901780.1443682191000@Atlassian.JIRA>
 <JIRA.12901780.1443682191531@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-8928) While adding VMs to LB rule,
 default NIC IP is always displayed rather than the IP corresponding to the
 NIC where LB is being created
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF GitHub Bot commented on CLOUDSTACK-8928:
--------------------------------------------

Github user nitin-maharana commented on the pull request:

    https://github.com/apache/cloudstack/pull/903#issuecomment-146101066
  
    @runseb I think there is no automated tests for this. I will try to write one. Thanks.


> While adding VMs to LB rule, default NIC IP is always displayed rather than the IP corresponding to the NIC where LB is being created
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-8928
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8928
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Nitin Kumar Maharana
>
> Issue  : 
> ---------
> While creating LB rule, if the VM belongs to multiple NICs, always the default NIC IP is the only one displayed. This causes issues in cases where we want to create an LB using the non-default NIC of the VM. It fails with an error message. This IP is never displayed in UI and only way is use the API directly to create such an LB rule.
> Steps
> =====
> 1. Create a VM with multiple NICs (VM belongs to multiple networks)
> 2. Navigate to the non-default Network of the VM -> IP Address -> Configuration -> Load Balancing -> Create an LB rule -> Add -> Choose the VM created
> Observe that the IP listed does not belong to that Network. It is always the IP of the default NIC. By choosing this IP, the LB creation will fail since the IP and network ids would not match.


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