cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sowmya Krishnan (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3464) [UI] [VPC] Associated network name displayed against Public IP acquired in a VPC is incorrect
Date Fri, 16 Aug 2013 04:05:47 GMT


Sowmya Krishnan commented on CLOUDSTACK-3464:

Could you try to reproduce this in your setup? Its quite simple and I've given the detailed
steps as well.

Just create a VPC, couple of network tiers, a VM in each tier and acquire IPs. Then create
an LB rule in one tier and SNAT in another. You should see the problem

If you still need a DB dump, it may have to wait, I don't have one currently running off CS
> [UI] [VPC] Associated network name displayed against Public IP acquired in a VPC is incorrect
> ---------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3464
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>         Environment: 4.2 branch
>            Reporter: Sowmya Krishnan
>            Assignee: Jessica Wang
>             Fix For: 4.2.0
>         Attachments: CLOUDSTACK-3464.png
> Create a VPC and few network tiers in the VPC. Acquire Public IP and associate each public
IP with a different network. One for LB, another for static NAT and so on.
> Click on Public IP address -> The associated network name is incorrect although the
network id is correct. API response is correct but UI maps the network name incorrectly.
> Steps:
> ====
> Create VPC 
> Create multiple network tiers - one with LB and rest without LB
> Acquire Public IP
> Create an LB rule in first tier. 
> Create Static NAT rule with another IP in second tier
> Click on VPC -> Router -> Public IP Addresses -> Choose each IP.
> Network name displayed is always the first tier
> Firebug log:
> { "listpublicipaddressesresponse" : { "count":1 ,"publicipaddress" : [  {"id":"163bf336-01e0-4e13-8e7f-eae520024faa","ipaddress":"","allocated":"2013-07-11T14:12:52+0530","zoneid":"2e15553c-0639-4304-823c-363354987b46","zonename":"BLR","issourcenat":false,"account":"admin","domainid":"9468b79e-e93e-11e2-b5cd-ca9c098803af","domain":"ROOT","forvirtualnetwork":true,"vlanid":"1e469cc6-19a8-48c5-ac84-97aaad5ecf66","vlanname":"100","isstaticnat":true,"issystem":false,"virtualmachineid":"22b1f160-04d8-424d-9640-a56d36692ce3","vmipaddress":"","virtualmachinename":"22b1f160-04d8-424d-9640-a56d36692ce3","virtualmachinedisplayname":"22b1f160-04d8-424d-9640-a56d36692ce3","associatednetworkid":"9bf72281-07fc-4f6e-bb02-5d99d9c6ec2e","associatednetworkname":"T3","networkid":"d323610b-3e2f-47a0-8c99-243d6e20d7d2","state":"Allocated","physicalnetworkid":"092fce46-5884-4c20-a286-28535caf6779","vpcid":"4820f7fc-528c-464f-9582-fa1be18c2ac4","tags":[],"isportable":false}
] } }
> As per response above, associatednetworkname":"T3", but in UI, T1 is displayed instead
for all IPs. Network id displayed is correct.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message