You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rajani Karuturi (JIRA)" <ji...@apache.org> on 2014/11/26 05:12:24 UTC

[jira] [Updated] (CLOUDSTACK-6717) [OVS][UI]VPC network creation page does not display custom network offering created for vpc

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

Rajani Karuturi updated CLOUDSTACK-6717:
----------------------------------------
    Fix Version/s:     (was: 4.4.0)
                   4.4.3

> [OVS][UI]VPC network creation page does not display custom network offering created for vpc
> -------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6717
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6717
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.4.0
>         Environment: Latest build from 4.4 branch with commit e6961fd21bb6d793302c234d0f409f66dc498072
>            Reporter: Sanjeev N
>            Assignee: Sanjeev N
>            Priority: Critical
>             Fix For: 4.4.3
>
>         Attachments: vpc_tier.PNG
>
>
> [SDN][UI]VPC network creation page does not display custom network offering created for vpc
> Steps to Reproduce:
> ================
> 1.Bring up CS in advanced zone with xen cluster
> 2.Create physical network with GRE isolation
> 3.Create Region level vpc
> 4.Create isolated network offering for vpc with virtualnetworking service and ovs as the service provider
> 5.Enable the network offering
> 6.In region level vpc try to create tier with above created network offering
> Result:
> ======
> Add tier in VPC page does not display the custom vpc offering created with ovs provider. It only shows the default vpc offerings in the drop down list.
> Attaching screen shot to describe the issue.



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