cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
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
Date Thu, 01 Oct 2015 07:01:04 GMT

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

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

GitHub user nitin-maharana opened a pull request:

    https://github.com/apache/cloudstack/pull/903

    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

    While calling the listNics API, instead of sending the default nic id as parameter, it
should send the network id as a parameter.
    
    So, replaced that nicid parameter as networkid parameter.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nitin-maharana/cloudstack nitin1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/903.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #903
    
----
commit 38d9b6a5457f0abc592cee7eb95ad7cb6fb303bf
Author: Nitin Kumar Maharana <nitinkumar.maharana@citrix.com>
Date:   2015-10-01T07:04:55Z

    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
    
    While calling the listNics API, instead of sending the default nic id as parameter, it
should send the network id as a parameter.
    So, replaced that nicid parameter as networkid parameter.

----


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

Mime
View raw message