[
https://issues.apache.org/jira/browse/CLOUDSTACK-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkata swamybabu budumuru closed CLOUDSTACK-4037.
--------------------------------------------------
GSLB is clean up is happening without any issues. closing this bug.
> [GSLB] removeFromGSLBRule is not cleaning the cloudsite1 infro from the
> second site NetScaler device
> ----------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4037
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4037
> 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
> Environment: commit id # 9cd4e089a5798f422961940efbf8ae33ed906b87
> Reporter: venkata swamybabu budumuru
> Assignee: Murali Reddy
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Have latest CloudStack setup with at least 2 advanced zones where each
> zone is configured with GSLB.
> 2. As a non-ROOT domain user,
> (a) Create 2 LB rules in each zone (LB1Zone1, LB1Zone2) using VR as the LB
> provider.
> (b) Create GSLB rule
> (c) Assign LB1Zone1 to the above GSLB rule. (At this point cloudsite1,
> vserver and services gets configured on Zone1 GSLB device.
> (d) Assign LB1Zone2 to the above GSLB rule. (At this moment, cloudsite1 and 2
> gets configured on both GSLB devices in zones)
> (c) remove LB1Zone2 from GSLB rule. (This action cleaned cloudsite2 info from
> both the devices)
> (d) remove LB1Zone1 from GSLB rule.
> Observations:
> (i) The above action cleaned cloudsite1 in from only GSLB device in zone1
> but, not from zone2.
> Attaching all the required logs along with db dump to the bug.
--
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
