[ https://issues.apache.org/jira/browse/CLOUDSTACK-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nitin Kumar Maharana resolved CLOUDSTACK-8928. ---------------------------------------------- Resolution: Fixed > 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)