cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <>
Subject [jira] [Assigned] (CLOUDSTACK-240) Create-Tag feature is not avialable for VPN Customer Gateway
Date Fri, 29 Mar 2013 17:49:15 GMT


Alena Prokharchyk reassigned CLOUDSTACK-240:

    Assignee: Brian Federle  (was: Alena Prokharchyk)

Java part of the code is fixed; reassigning the bug to the UI team.

For QA to test:

1) Test that you can create/list tags for RemoteAccessGateway
2) Regression test for vpn lifecycle - enableVpn/disableVpn/add user; restart network and
restart the VR when VPN is configured on a source nat ip address
3) DB upgrade testing:

* being on previous version, create couple of remote access vpns.
* after the upgrade check the remote_access_vpn table. 2 new fields should be added - id and
uuid. Make sure that both fields have the values for all the records in the table.
> Create-Tag feature is not avialable for  VPN Customer Gateway
> -------------------------------------------------------------
>                 Key: CLOUDSTACK-240
>                 URL:
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: pre-4.0.0
>            Reporter: prashant kumar mishra
>            Assignee: Brian Federle
>            Priority: Minor
>             Fix For: 4.2.0
> There is no option to tag VPN Customer Gateway.
> Steps to check 
> ----------------------
> ----------------------
> 1-Go to network tab
> 2-From select view select VPN Customer Gateway 
> 3- Click on add VPN Customer Gateway
> 5-Select the VPN Customer Gateway 
> 6-there is no option to create/add Tag for VPN Customer Gateway
> Release Planning:
> Dev List Discussion: Unknown
> Functional Spec: N/A
> Feature Branch:  Unknown
> Documentation: Not needed
> QA: Needs to be tested

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