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

ASF subversion and git services commented on CLOUDSTACK-8984:
-------------------------------------------------------------

Commit 73c6c6c96b227ec2843c0c6bc5ce7f6d7205ee4f in cloudstack's branch 
refs/heads/master from [~remibergsma]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=73c6c6c ]

Merge pull request #996 from karuturi/CLOUDSTACK-8984

[4.6] CLOUDSTACK-8984: VPC Network offerings tab missing from UIThis is a 
regression from commit af2f21894ce061faadc8cec29b901719303a29dc

added vpcofferings to the select list

Before the change (from the bug):
![offerings_46](https://cloud.githubusercontent.com/assets/186833/10781847/34ae9bc4-7d71-11e5-8159-b90422ef34f6.png)

After the change:
![screen shot 2015-10-28 at 12 32 59 
pm](https://cloud.githubusercontent.com/assets/186833/10781850/3ef96500-7d71-11e5-84c5-34589ec10bf9.png)

* pr/996:
  CLOUDSTACK-8984: VPC Network offerings tab missing from UI

Signed-off-by: Remi Bergsma <git...@remi.nl>


> VPC Network offerings tab missing from UI
> -----------------------------------------
>
>                 Key: CLOUDSTACK-8984
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8984
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: UI
>    Affects Versions: 4.6.0
>            Reporter: Remi Bergsma
>            Assignee: Rajani Karuturi
>            Priority: Critical
>         Attachments: offerings_44.png, offerings_46.png
>
>
> Home - Service Offerings - Network Offerings
> There used to be a tab to display the VPC offerings, but it's no longer 
> there. See difference in screenshots. It was there in 4.4.4.
> Please add it again as you cannot add VPC offerings now (only through the 
> API).



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

Reply via email to