You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Murali Reddy (JIRA)" <ji...@apache.org> on 2013/07/01 15:43:20 UTC
[jira] [Resolved] (CLOUDSTACK-3280) [GSLB] Clean up of lb monitors
is not happening as part of deleteGSLBRule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Murali Reddy resolved CLOUDSTACK-3280.
--------------------------------------
Resolution: Fixed
This is fixed as part of the commit 1032d5c26a3f5573e5cdb695038be2cce1c19fa3 for the bug CLOUDSTACK-3282.
> [GSLB] Clean up of lb monitors is not happening as part of deleteGSLBRule
> -------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3280
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3280
> 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-10.147.44.66 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: http://www.atlassian.com/software/jira