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 Mon, 02 Nov 2015 11:36:27 GMT

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

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

Github user karuturi commented on the pull request:

    https://github.com/apache/cloudstack/pull/903#issuecomment-152994809
  
    great find @nitin-maharana 
    manually tested the fix
    In my setup, I had a vm with two nics 
    isolated1 - 	10.1.1.14 - default
    isolated 2 - 	10.1.1.187 - non default
    
    When I add a LB rule in network isolated2 for the VM, this is API call before the change
and it failed.
    ![screen shot 2015-11-02 at 4 38 35 pm](https://cloud.githubusercontent.com/assets/186833/10880698/76c4510a-8183-11e5-9d2a-6e912ea45f94.png)
    
    After the fix, it took the right IP and succeeded. 
    ![screen shot 2015-11-02 at 4 49 11 pm](https://cloud.githubusercontent.com/assets/186833/10880712/85c690be-8183-11e5-8c76-fe39edb50caa.png)
    
    :+1: LGTM



> 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