[
https://issues.apache.org/jira/browse/CLOUDSTACK-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695913#comment-13695913
]
venkata swamybabu budumuru commented on CLOUDSTACK-3284:
--------------------------------------------------------
Same is the case with REVOKE state.
(1) Try to delete GSLB rule while the GSLB provider is not reachable
Observations:
(i) It will fail to cleanup and it leaves the rule in Revoke state forever.
> [GSLB] GSLBRule state stuck in "Add" if there is anyting wrong happens during
> the assignToGloabalLBRule
> -------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3284
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3284
> 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
> Priority: Minor
> Fix For: 4.2.0
>
>
> Steps to reproduce:
> 1. Have latest CS setup with at least 2 advanced zones.
> 2. Enable each zone with Netscaler with GSLB
> 3. As a non-ROOT domain user, create a GSLB rule
> 4. assign one LB rule (using VR) from zone1.
> 5. assign another LB rule from another zone2.
> Observations:
> (i) second LB rule assignment failed with the following error "Failed to
> configure GSLB rule in the zone"
> (ii) When the above operations failed, the state of the LB rule just stuck in
> "Add" state.
--
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
