cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alena Prokharchyk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2726) Adding VMs to LB rule is failing with "Unexpected exception while executing org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd com.cloud.utils.exception.CloudRuntimeException:"
Date Tue, 28 May 2013 19:24:19 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668581#comment-13668581
] 

Alena Prokharchyk commented on CLOUDSTACK-2726:
-----------------------------------------------

The load balancer command failed on the backend:
===============================================

2013-05-28 17:19:37,046 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-31:null) Seq
1-257491068: Response Received:
2013-05-28 17:19:37,046 DEBUG [agent.transport.Request] (DirectAgent-31:null) Seq 1-257491068:
Processing:  { Ans: , MgmtId: 90310994128556, via: 1, Ver: v1, Flags: 0, [{"Answer":{"result":false,"details":"LoadBa
lancerConfigCommand failed","wait":0}}] }
2013-05-28 17:19:37,046 DEBUG [agent.transport.Request] (Job-Executor-9:job-45) Seq 1-257491068:
Received:  { Ans: , MgmtId: 90310994128556, via: 1, Ver: v1, Flags: 0, { Answer } }

Somebody familiar with the VR script, should look at it.
                
> Adding VMs to LB rule is failing with "Unexpected exception while executing org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd
com.cloud.utils.exception.CloudRuntimeException:"
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2726
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2726
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.0.2
>            Reporter: Abhinav Roy
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: management-server.log.2013-05-28
>
>
> Adding VMs to Lb rule is failing with :
> 2013-05-28 17:19:37,049 WARN  [network.lb.LoadBalancingRulesManagerImpl] (Job-Executor-9:job-45)
Unable to apply the load balancer config because resource is unavaliable.
> com.cloud.exception.ResourceUnavailableException: Resource [DataCenter:1] is unreachable:
Unable to apply loadbalancing rules on router 
>         at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyRules(VirtualNetworkApplianceManagerImpl.java:3739)
>         at com.cloud.network.router.VirtualNetworkApplianceManagerImpl.applyLoadBalancingRules(VirtualNetworkApplianceManagerImpl.java:3604)
>         at com.cloud.network.element.VirtualRouterElement.applyLBRules(VirtualRouterElement.java:393)
>         at com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:1509)
>         at com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLbRules(LoadBalancingRulesManagerImpl.java:2047)
>         at com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerRules(LoadBalancingRulesManagerImpl.java:1546)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerConfig(LoadBalancingRulesManagerImpl.java:1466)
>         at com.cloud.network.lb.LoadBalancingRulesManagerImpl.assignToLoadBalancer(LoadBalancingRulesManagerImpl.java:1002)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd.execute(AssignToLoadBalancerRuleCmd.java:100)
>         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:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-05-28 17:19:37,057 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-45)
Unexpected exception while executing org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd
> com.cloud.utils.exception.CloudRuntimeException: Failed to add specified loadbalancerruleid
for vms [18]
>         at com.cloud.network.lb.LoadBalancingRulesManagerImpl.assignToLoadBalancer(LoadBalancingRulesManagerImpl.java:1025)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at org.apache.cloudstack.api.command.user.loadbalancer.AssignToLoadBalancerRuleCmd.execute(AssignToLoadBalancerRuleCmd.java:100)
>         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:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-05-28 17:19:37,058 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-9:job-45)
Complete async job-45, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text:
Failed to add specified loadbalancerruleid for vms [18]
> 2013-05-28 17:19:37,081 DEBUG [cloud.async.SyncQueueManagerImpl] (Job-Executor-9:job-45)
Sync queue (4) is currently empty
> 2013-05-28 17:19:37,251 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===START===
 10.144.7.12 -- GET  command=queryAsyncJobResult&jobId=c5799963-5a01-4292-b2b2-8d8a569926d2&response=json&sessionkey=w9jbTBlzxF4olPO4dlqBK01LRX8%3D&_=1369741804446
> 2013-05-28 17:19:37,263 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-10:null)
Async job-45 completed
> 2013-05-28 17:19:37,269 DEBUG [cloud.api.ApiServlet] (catalina-exec-10:null) ===END===
 10.144.7.12 -- GET  command=queryAsyncJobResult&jobId=c5799963-5a01-4292-b2b2-8d8a569926d2&response=json&sessionkey=w9jbTBlzxF4olPO4dlqBK01LRX8%3D&_=1369741804446
> Note : The issue is seen with all kinds of LB rules, with VR , VPCVR or InternalLbVM
> When VMs are added to the LB rule , this error message is seen but in the DB and UI we
see those VMs as part of LB
> Marking it as blocker because I am not able top proceed with my testing for "Internal
Load Balancing of VPC tier" feature due to this.

--
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

Mime
View raw message