cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinandan Prateek (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3973) [GSLB] [LOGS Message] Improving logs messages for GSLB rule configuration
Date Thu, 10 Oct 2013 06:38:41 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhinandan Prateek updated CLOUDSTACK-3973:
-------------------------------------------

    Fix Version/s:     (was: 4.2.1)
                   4.3.0

> [GSLB] [LOGS Message] Improving logs messages for GSLB rule configuration
> -------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3973
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3973
>             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 # 6275d697e340be5b520f37b15d72343fa47c00a9
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>             Fix For: 4.3.0
>
>         Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Have latest cloudstack with at least 2 advanced zones where each zone is configure
with GSLB provider.
> 2. Create LB rule in each zone using VR (LB rule 1 in zone1 and LB rule 2 in zone2)
> 3. As a non-ROOT domain user, create a GSLB rule and map LBrule1.
> Observations:
> (i) This will create GSLB site, vserver, service in zone1 netscaler
> 4. now map LBRule2 to the above GSLB rule.
> (ii) This will create GSLB site2 on netscaler devices in both the zones. During this
process, this will end up in configuring site1, vserver, service in Zone1 NS device again
and throws log message like below. This is little confusing and gives an impression that something
went wrong. it would be good to change these message to be little more informative.
> 2013-07-31 14:28:23,869 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-93:null)
Seq 9-712310787: Executing request
> 2013-07-31 14:28:23,973 DEBUG [network.resource.NetscalerResource] (DirectAgent-93:null)
Failed to add GSLB virtual server: cloud-gslb-vserver-GSLB1.xyztelco.com due to Resource already
exists
> 2013-07-31 14:28:24,085 WARN  [network.resource.NetscalerResource] (DirectAgent-93:null)
Retrying GlobalLoadBalancerConfigCommand. Number of retries remaining: 1
> 2013-07-31 14:28:24,158 DEBUG [network.resource.NetscalerResource] (DirectAgent-93:null)
Successfully added GSLB virtual server: cloud-gslb-vserver-GSLB1.xyztelco.com
> 2013-07-31 14:28:24,258 DEBUG [network.resource.NetscalerResource] (DirectAgent-93:null)
Successfully updated GSLB site: cloudsite1
> 2013-07-31 14:28:24,356 DEBUG [network.resource.NetscalerResource] (DirectAgent-93:null)
Successfully created service: cloud-gslb-service-cloudsite1-10.147.44.64-22 at site: cloudsite1
> 2013-07-31 14:28:24,474 WARN  [network.resource.NetscalerResource] (DirectAgent-93:null)
Failed to bind monitor to GSLB service due to The monitor is already bound to the service
> 2013-07-31 14:28:24,562 DEBUG [network.resource.NetscalerResource] (DirectAgent-93:null)
Successfully created GSLB site: cloudsite2
> 2013-07-31 14:28:24,692 DEBUG [network.resource.NetscalerResource] (DirectAgent-93:null)
Successfully created service: cloud-gslb-service-cloudsite2-10.147.54.63-22 at site: cloudsite2
> 2013-07-31 14:28:24,730 DEBUG [network.resource.NetscalerResource] (DirectAgent-93:null)
Successfully created service: cloud-gslb-service-cloudsite2-10.147.54.63-22 and virtual server:
cloud-gslb-vserver-GSLB1.xyztelco.com binding



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message