venkata swamybabu budumuru created CLOUDSTACK-4048:
------------------------------------------------------
Summary: [GSLB] Failed to assign more than one LB rule to a GSLB
rule that is created with gslbmethod=leastconn
Key: CLOUDSTACK-4048
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4048
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 id # 9cd4e089a5798f422961940efbf8ae33ed906b87
Reporter: venkata swamybabu budumuru
Assignee: Murali Reddy
Priority: Critical
Fix For: 4.2.0
Steps to reproduce:
1. Have latest CloudStack setup with at least 2 zones which are GSLB enabled.
2. create LB1Zone1, LB1Zone2 rules in each zone.
3. Create a GSLB rule with gslbmethod=leastconn
2013-08-02 14:32:54,633 DEBUG [cloud.api.ApiServlet] (catalina-exec-19:null)
===START=== 10.252.192.25 -- GET
command=createGlobalLoadBalancerRule&response=json&sessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3D&name=test1®ionid=1&gslblbmethod=leastconn&gslbstickysessionmethodname=sourceip&gslbdomainname=test1&gslbservicetype=udp&description=test1&_=1375434184015
4. Assign LB1Zone1 to the above GSLB rule
command=assignToGlobalLoadBalancerRule&response=json&sessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3D&id=44be9c74-40b8-49ea-af7f-3e95fdf18230&loadbalancerrulelist=06dae3f7-b65f-4f14-ae75-c2c22cbdaa40&_=1375434216924
2013-08-02 14:33:27,796 DEBUG [network.resource.NetscalerResource]
(DirectAgent-126:null) Successfully added GSLB virtual server:
cloud-gslb-vserver-test1.xyztelco.com
2013-08-02 14:33:27,883 DEBUG [network.resource.NetscalerResource]
(DirectAgent-126:null) Successfully created GSLB site: cloudsite1
2013-08-02 14:33:28,048 DEBUG [network.resource.NetscalerResource]
(DirectAgent-126:null) Successfully created service:
cloud-gslb-service-cloudsite1-10.147.44.68-22 at site: cloudsite1
2013-08-02 14:33:28,079 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-11:null) Ping from 1
2013-08-02 14:33:28,080 DEBUG [network.resource.NetscalerResource]
(DirectAgent-126:null) Successfully created service:
cloud-gslb-service-cloudsite1-10.147.44.68-22 and virtual server:
cloud-gslb-vserver-test1.xyztelco.com binding
2013-08-02 14:33:28,178 DEBUG [network.resource.NetscalerResource]
(DirectAgent-126:null) Successfully added virtual server:
cloud-gslb-vserver-test1.xyztelco.com domain name: test1.xyztelco.com binding
5. assign another LB1Zone2 rule to the above GSLB rule
command=assignToGlobalLoadBalancerRule&response=json&sessionkey=1IRoAIDCuI6havGghvm3MFWPlxY%3D&id=44be9c74-40b8-49ea-af7f-3e95fdf18230&loadbalancerrulelist=ae92ca25-7c33-4545-a329-01602fb80daa&_=1375434245185
Observations:
(i) Seen the following error in mgmt server logs.
2013-08-02 14:33:56,094 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-440:null) Seq 9-788267021: Executing request
2013-08-02 14:33:56,164 DEBUG [network.resource.NetscalerResource]
(DirectAgent-440:null) Failed to add GSLB virtual server:
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,320 WARN [network.resource.NetscalerResource]
(DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of
retries remaining: 1
2013-08-02 14:33:56,382 DEBUG [network.resource.NetscalerResource]
(DirectAgent-440:null) Failed to add GSLB virtual server:
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,433 WARN [network.resource.NetscalerResource]
(DirectAgent-440:null) Retrying GlobalLoadBalancerConfigCommand. Number of
retries remaining: 0
2013-08-02 14:33:56,436 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-11845: Processing Seq 3-11845: { Cmd ,
MgmtId: -1, via: 3, Ver: v1, Flags: 11,
[{"com.cloud.agent.api.ConsoleProxyLoadReportCommand":{"_proxyVmId":2,"_loadInfo":"{\n
\"connections\": []\n}","wait":0}}] }
2013-08-02 14:33:56,447 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-6:null) SeqA 3-11845: Sending Seq 3-11845: { Ans: ,
MgmtId: 7280707764394, via: 3, Ver: v1, Flags: 100010,
[{"com.cloud.agent.api.AgentControlAnswer":{"result":true,"wait":0}}] }
2013-08-02 14:33:56,479 DEBUG [network.resource.NetscalerResource]
(DirectAgent-440:null) Failed to add GSLB virtual server:
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,479 DEBUG [agent.manager.DirectAgentAttache]
(DirectAgent-440:null) Seq 9-788267021: Response Received:
2013-08-02 14:33:56,480 DEBUG [agent.transport.Request] (DirectAgent-440:null)
Seq 9-788267021: Processing: { Ans: , MgmtId: 7280707764394, via: 9, Ver: v1,
Flags: 10,
[{"com.cloud.agent.api.routing.GlobalLoadBalancerConfigAnswer":{"result":false,"details":"Failed
to apply GSLB configuration due to Failed to add GSLB virtual server:
cloud-gslb-vserver-test1.xyztelco.com due to Arguments cannot both be specified
[netmask, lbMethod==LEASTCONNECTION]","wait":0}}] }
2013-08-02 14:33:56,480 DEBUG [agent.transport.Request]
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Seq
9-788267021: Received: { Ans: , MgmtId: 7280707764394, via: 9, Ver: v1, Flags:
10, { GlobalLoadBalancerConfigAnswer } }
2013-08-02 14:33:56,480 DEBUG [agent.manager.AgentManagerImpl]
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) 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-test1.xyztelco.com due to Arguments cannot both be specified
[netmask, lbMethod==LEASTCONNECTION]
2013-08-02 14:33:56,480 DEBUG [network.element.NetscalerElement]
(Job-Executor-129:job-99 = [ 8f691f76-84a7-408d-b3c9-6d028e9ad76c ]) Unable to
apply global load balancer rule to the gslb service provid
er in zone
Attaching all the required logs along with db dump to the bug.
--
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
