Sailaja Mada created CLOUDSTACK-220:
---------------------------------------
Summary: Error while configuring Loadbalncing Rules when Netscaler
is used as Load Balancer
Key: CLOUDSTACK-220
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-220
Project: CloudStack
Issue Type: Bug
Components: Network Devices
Affects Versions: pre-4.0.0
Reporter: Sailaja Mada
Setup:
Management Server is on RHEL 6.3 , Hypervisor : Xen 6.0.2 , Netscaler is 9.3
VPX
Steps :
1. Configure Advanced Networking Zone
2. Add Netscaler device and enable it
3. Create a new account and Network offering with DNS,DHCP,Source NAT as
Virtual Router , Load Balancing as Netscaler .
4. Create Network using this offering
5. Deploy the instance using this network
6. Access Guest Network Configuration, Acquire New Public IP
7. Configure Load balancing rule with 80 to 80
Observation :
Error is observed while adding LB rules :
Unable to identify the provider by name F5ExternalLoadBalancerElement.
2012-09-27 13:27:01,755 DEBUG [cloud.network.NetworkManagerImpl]
(Job-Executor-28:job-22) Network Rules for network 204 were handled by
Netscaler
2012-09-27 13:27:01,762 ERROR [cloud.api.ApiDispatcher]
(Job-Executor-28:job-22) Exception while executing
RemoveFromLoadBalancerRuleCmd:
com.cloud.utils.exception.CloudRuntimeException: Unable to identify the
provider by name F5ExternalLoadBalancerElement
at
com.cloud.network.NetworkManagerImpl.applyRules(NetworkManagerImpl.java:3677)
at
com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerRules(LoadBalancingRulesManagerImpl.java:922)
at
com.cloud.utils.db.DatabaseCallback.intercept(DatabaseCallback.java:34)
at
com.cloud.network.lb.LoadBalancingRulesManagerImpl.applyLoadBalancerConfig(LoadBalancingRulesManagerImpl.java:896)
at
com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeFromLoadBalancerInternal(LoadBalancingRulesManagerImpl.java:527)
at
com.cloud.network.lb.LoadBalancingRulesManagerImpl.removeFromLoadBalancer(LoadBalancingRulesManagerImpl.java:501)
at
com.cloud.event.ActionEventCallback.intercept(ActionEventCallback.java:36)
at
com.cloud.api.commands.RemoveFromLoadBalancerRuleCmd.execute(RemoveFromLoadBalancerRuleCmd.java:99)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
at
com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:432)
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)
2012-09-27 13:27:01,763 DEBUG [cloud.async.AsyncJobManagerImpl]
(Job-Executor-28:job-22) Complete async job-22, jobStatus: 2, resultCode: 530,
result: Error Code: 530 Error text: Unable to identify the provider by name
F5ExternalLoadBalancerElement
2012-09-27 13:27:01,787 DEBUG [cloud.async.SyncQueueManagerImpl]
(Job-Executor-28:job-22) Sync queue (1) is currently empty
2012-09-27 13:27:02,938 DEBUG [cloud.async.AsyncJobManagerImpl]
(catalina-exec-20:null) Async job-22 completed
Netscaler :
VLAN are created, LB server is created.
> sh ru | grep Cloud
add server Cloud-Server--10.0.33.182 10.0.33.182
add service Cloud-Service-10.0.33.182-80 Cloud-Server--10.0.33.182 HTTP 80
-gslb NONE -maxClient 0 -maxReq 0 -cip DISABLED -usip NO -useproxyport YES -sp
ON -cltTimeout 180 -svrTimeout 360 -CKA NO -TCPB NO -CMP NO
add lb vserver Cloud-VirtualServer-10.102.125.73-80 HTTP 10.102.125.73 80
-persistenceType NONE -lbMethod ROUNDROBIN -cltTimeout 180
bind lb vserver Cloud-VirtualServer-10.102.125.73-80
Cloud-Service-10.0.33.182-80
> sh vlan
1) VLAN ID: 1
Member Interfaces : 1/1 1/2 LO/1 Tagged: None
2) VLAN ID: 300 VLAN Alias Name:
Member Interfaces : 1/2 Tagged: 1/2
IP: 10.0.3.85 Mask: 255.255.240.0
4) VLAN ID: 302 VLAN Alias Name:
Member Interfaces : 1/2 Tagged: 1/2
IP: 10.0.39.93 Mask: 255.255.240.0
Done
Attached logs.
--
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
