[jira] [Resolved] (CLOUDSTACK-5719) [UI] Not listing shared network offerings tagged on second physical network

["Jessica Wang (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jessica Wang resolved CLOUDSTACK-5719.
--------------------------------------
    Resolution: Fixed

Sowmya,

thanks a lot for your database dump!!!    ^_^

Jessica

> [UI] Not listing shared network offerings tagged on second physical network
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5719
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5719
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.3.0
>         Environment: Advanced zone, multiple guest networks
>            Reporter: Sowmya Krishnan
>            Assignee: Jessica Wang
>             Fix For: 4.4.0
>
>         Attachments: cloud.dmp.gz, createsharednw.png
>
>
> Create multiple physical networks with guest networks in both physical networks.
> Tag the guest networks and use those while creating shared network offerings 
> Try to create shared network in both physical networks
> UI:
> Networks -> Add guest network -> Choose the second physical n/w
> Result:
> Lists shared network offering belonging to physical n/w 1 although I choose the second physical n/w
> Firebug logs shows that it always queries Network offering for the same tag (tag1) although we have 2 tags, one for each physical network:
> http://10.102.192.125:8080/client/api?command=listPhysicalNetworks&response=json&sessionkey=zFMtaefMr9NxN%2F0RjgCtbWLft%2FU%3D&zoneid=15ac37e8-635b-43f4-a53f-4a8c003c5912&_=1388662102005
> http://10.102.192.125:8080/client/api?command=listTrafficTypes&response=json&sessionkey=zFMtaefMr9NxN%2F0RjgCtbWLft%2FU%3D&physicalnetworkid=c19f422a-55a4-4473-867e-2c9c0b64fc9a&_=1388662102199
> http://10.102.192.125:8080/client/api?command=listTrafficTypes&response=json&sessionkey=zFMtaefMr9NxN%2F0RjgCtbWLft%2FU%3D&physicalnetworkid=5f9c1b69-325c-43ad-b05e-76470ddbe610&_=1388662102387
> http://10.102.192.125:8080/client/api?command=listNetworkOfferings&response=json&sessionkey=zFMtaefMr9NxN%2F0RjgCtbWLft%2FU%3D&state=Enabled&zoneid=15ac37e8-635b-43f4-a53f-4a8c003c5912&tags=tag1&guestiptype=Shared&_=1388662102490
> http://10.102.192.125:8080/client/api?command=listNetworkOfferings&response=json&sessionkey=zFMtaefMr9NxN%2F0RjgCtbWLft%2FU%3D&state=Enabled&zoneid=15ac37e8-635b-43f4-a53f-4a8c003c5912&tags=tag1&guestiptype=Shared&_=1388662102841
> Further, if we continue to create the shared network, it gets created in physical network 2 while the offering is actually tagged on physical n/w 1
> Workaround is to go to that physical network and add guest network from there
> zone -> physical network -> guest - configure ->  Network -> Add guest network



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