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/06/05 08:45:20 UTC
[jira] [Resolved] (CLOUDSTACK-2741) [GSLB] GSLB service doesn't
come up if the LB rule mapped to it is serviced by VR
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Murali Reddy resolved CLOUDSTACK-2741.
--------------------------------------
Resolution: Fixed
> [GSLB] GSLB service doesn't come up if the LB rule mapped to it is serviced by VR
> ---------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2741
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2741
> 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 # 80a3c0535e0a8ad3edba3713a61d063a176191d8
> Reporter: venkata swamybabu budumuru
> Assignee: Murali Reddy
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: logs.tgz, ns.output
>
>
> Steps to reproduce :
> 1. Have CS with at least 2 advanced zones (zone1, Zone2)
> 2. Each zone is configured with single physical network
> 3. Each physical network is configured with at least one GSLB device
> 4. LB is created in zone1 using VR as provider
> 5. LB rule is created in zone2 using same GSLB device (netscaler) as provider
> 6. Have at least one non-ROOT domain user
> 7. As the above user and create a GSLB rule then assign (4) & (5)
> Observations:
> i. GSLB sites got created successfully on each GSLB provider
> ii. GSLB server and service also created but, service that is linked to LB on VR shows state as 'Down'
> iii. Both the GSLB devices seeing the same issue.
> > show gslb service
> 1) cloud-gslb-service-cloudsite1-10.147.44.62-22 (10.147.44.62: 22)- TCP Server: Cloud-Server--10.147.44.62 State: UP
> Effective State: UP
> Max Conn: 0 Max Bandwidth: 0 kbits
> PublicIP: 10.147.44.62 PublicPort: 22
> Type: LOCAL Site Name: cloudsite1
> Site Persistence: NONE
> Threshold: BELOW Monitor Threshold : 0
> 2) cloud-gslb-service-cloudsite2-10.147.54.61-22 (10.147.54.61: 22)- TCP Server: Cloud-Server--10.147.54.61 State: DOWN
> Effective State: DOWN
> Max Conn: 0 Max Bandwidth: 0 kbits
> PublicIP: 10.147.54.61 PublicPort: 22
> Type: REMOTE Site Name: cloudsite2
> Client IP: DISABLED
> Down state flush: ENABLED
> Site Persistence: NONE
> Threshold: BELOW Monitor Threshold : 0
> (iv) When LB rules assigned to GSLB are from NetScaler then everything is fine.
> Attaching all the mgmt server logs along with db dump to the bug.
> uploading the different netscaler outputs as a file 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