You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "venkata swamybabu budumuru (JIRA)" <ji...@apache.org> on 2013/05/09 12:43:15 UTC
[jira] [Created] (CLOUDSTACK-2416) [GSLB] createGSLBRule domainName
restrictions need little more validation
venkata swamybabu budumuru created CLOUDSTACK-2416:
------------------------------------------------------
Summary: [GSLB] createGSLBRule domainName restrictions need little more validation
Key: CLOUDSTACK-2416
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2416
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Environment: commit # 09af15035b9febe6f55e73a1389f950ab042564f
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Priority: Minor
Steps to reproduce :
(1) Have CloudStack setup with at least 1 zone
(2) create a GSLB Rule. As part of this rule creation, send domainName of length 190 chars (make sure >127 chars)
Observations:-
(i) GSLB rule gets created successfully
(ii) While assigning LB rule to the GSLB, it fails with the following error. Looks like some intermediate variable datatype restriction imposed by CloudStack created this issue.
2013-05-09 11:22:33,032 DEBUG [agent.manager.AgentManagerImpl] (Job-Executor-136:job-280) Details from executing class com.cloud.agent.api.routing.GlobalLoadBalancerConfigCommand: Failed to apply GSLB configuration due to Failed to add GSLB virtual server: cloud-gslb-vserver-test1test1test1test1test1test1test1test1test1test1test1test1tes.test1test1test1test1test1test1test1test1test1test1test1test1tes.test1test1test1test1test1test1test1test1test1test1test1test1te.cloud.xyztelcom.com due to String length exceeds maximum [name, 127]
2013-05-09 11:22:33,032 DEBUG [network.element.NetscalerElement] (Job-Executor-136:job-280) Unable to apply global load balancer rule to the gslb service provider in zone 1
2013-05-09 11:22:33,032 WARN [region.gslb.GlobalLoadBalancingRulesServiceImpl] (Job-Executor-136:job-280) Failed to configure GSLB rul in the zone 1 due to Resource [DataCenter:1] is unreachable: Unable to apply global load balancer rule to the gslb service provider in zone 1
2013-05-09 11:22:33,033 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-136:job-280) Unexpected exception while executing org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd
com.cloud.utils.exception.CloudRuntimeException: Failed to configure GSLB rul in the zone
at org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.applyGlobalLoadBalancerRuleConfig(GlobalLoadBalancingRulesServiceImpl.java:595)
at org.apache.cloudstack.region.gslb.GlobalLoadBalancingRulesServiceImpl.assignToGlobalLoadBalancerRule(GlobalLoadBalancingRulesServiceImpl.java:254)
at org.apache.cloudstack.api.command.user.region.ha.gslb.AssignToGlobalLoadBalancerRuleCmd.execute(AssignToGlobalLoadBalancerRuleCmd.java:106)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
2013-05-09 11:22:33,034 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-136:job-280) Complete async job-280, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to configure GSLB rul in the zone
Attaching all the required logs along with db dump.
--
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