Francois Gaudreault created CLOUDSTACK-1543:
-----------------------------------------------
Summary: Cannot add another VM to an existing Load Balancing rule
when using the NetScaler
Key: CLOUDSTACK-1543
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1543
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Affects Versions: 4.0.1
Reporter: Francois Gaudreault
Priority: Critical
On CloudStack 4.0.1, when we try to add a VM to an existing NetScaler LB rule,
CloudStack returns an error. If we look into the stack trace, we can see that
CS is trying to add a new rule instead of modifying the existing one.
2013-03-06 10:21:51,512 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-24:job-262) Details from executing class
com.cloud.agent.api.routing.LoadBalancerConfigCommand: Exception:
com.cloud.utils.exception.ExecutionException
Message: Failed to create new virtual
server:Cloud-VirtualServer-74.121.246.130-80 due to This parameter is only
applicable to a MYSQL vserver.
Stack: com.cloud.utils.exception.ExecutionException: Failed to create new
virtual server:Cloud-VirtualServer-74.121.246.130-80 due to This parameter is
only applicable to a MYSQL vserver.
at
com.cloud.network.resource.NetscalerResource.addLBVirtualServer(NetscalerResource.java:1377)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:437)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:345)
at
com.cloud.network.resource.NetscalerResource.retry(NetscalerResource.java:1456)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:575)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:345)
at
com.cloud.network.resource.NetscalerResource.retry(NetscalerResource.java:1456)
at
com.cloud.network.resource.NetscalerResource.execute(NetscalerResource.java:575)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:345)
at
com.cloud.network.resource.NetscalerResource.executeRequest(NetscalerResource.java:334)
at
com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:191)
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.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
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)
Seen on CS 4.0.1 nonoss build with NetScaler 10.0 build 73.5
--
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
