cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <>
Subject [jira] [Closed] (CLOUDSTACK-3280) [GSLB] Clean up of lb monitors is not happening as part of deleteGSLBRule
Date Fri, 02 Aug 2013 09:15:49 GMT


venkata swamybabu budumuru closed CLOUDSTACK-3280.

Verified this issue with latest build and found that deleteGSLBRule cleans the lb monitors
automatically. Closing this issue.
> [GSLB] Clean up of lb monitors is not happening as part of deleteGSLBRule
> -------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3280
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
> Steps to reproduce:
> 1.Have a latest CS setup with at least 2 advanced zone running XenServer
> 2. Add Netscaler and enable it for GSLB in each zone
> 3. As a non-ROOT domain user, create a GSLB rule
> 4. assign one LB rule (using VR) from any of the zone.
> 5. delete GSLB rule 
> Observations:- 
> (i) GSLB rule get delete successfully without any issues from CloudStack
> (ii) but, on NetScaler, deleteGSLBRule is not cleaning the lb monitor that was created
automatically as part of step:4
> Here is the snippet from NS.
> # show lb monitor TCP
> 20)   Name.......:cloud-monitor-  Type......:       TCP                 
                             State....:   ENABLED
> Attaching all the logs along with db dump from mgmt server

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