cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2914) Regression: With introduction of internal lb provider one must specify the lbScheme when creating network offerings (backward compat)
Date Mon, 10 Jun 2013 10:15:20 GMT

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

ASF subversion and git services commented on CLOUDSTACK-2914:
-------------------------------------------------------------

Commit 20c1f2c3466926163ccf0fe1487b3ca61d35da07 in branch refs/heads/master from [~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=20c1f2c ]

CLOUDSTACK-2914: lbScheme Public should be specified in NetworkOffering

NetworkOfferings now require a mandatory scheme in the
serviceCapabilityList to create a VPC loadbalancer on the public side.
This commit fixes the test for VPC networks. Additionally there needs to
be a fix for making this the default behaviour so as not to hurt the
backwards compatibility.

test still fails because of CLOUDSTACK-2915 however which is a related
network ACL backwards compat issue. See bug for more details.

Signed-off-by: Prasanna Santhanam <tsp@apache.org>

                
> Regression: With introduction of internal lb provider one must specify the lbScheme when
creating network offerings (backward compat)
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2914
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2914
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, Doc, Network Controller
>    Affects Versions: 4.2.0
>            Reporter: Prasanna Santhanam
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> If you choose to have LB in your VPC (by default on the public side) you will need to
specify the lbScheme in the serviceCapability list when creating the network offering or LB
creation when the network is implemented will fail.
> Following automated test fails:
> <nose.suite.ContextSuite context=TestVPCNetworkGc>:setup (from nosetests)
> Failing for the past 14 builds (Since #11 )
> Took 16 min.
> add description
> Error Message
> Execute cmd: createloadbalancerrule failed, due to: errorCode: 530, errorText:Failed
to create load balancer rule: SSH
> Stacktrace
> Traceback (most recent call last):
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
line 208, in run
>     self.setUp()
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
line 291, in setUp
>     self.setupContext(ancestor)
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/suite.py",
line 314, in setupContext
>     try_run(context, names)
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/nose/util.py",
line 469, in try_run
>     return func()
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/test/integration/component/test_vpc_network.py",
line 2238, in setUpClass
>     domainid=cls.account.domainid
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/integration/lib/base.py",
line 1498, in create
>     return LoadBalancerRule(apiclient.createLoadBalancerRule(cmd).__dict__)
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py",
line 893, in createLoadBalancerRule
>     response = self.connection.marvin_request(command, response_type=response, method=method)
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/cloudstackConnection.py",
line 223, in marvin_request
>     response = jsonHelper.getResultObj(response.json(), response_type)
>   File "/var/lib/jenkins/workspace/test-regression-matrix/suite/test_vpc_network/24/lib/python2.7/site-packages/marvin/jsonHelper.py",
line 128, in getResultObj
>     raise cloudstackException.cloudstackAPIException(responseName.replace("response",
""), errMsg)
> cloudstackAPIException: Execute cmd: createloadbalancerrule failed, due to: errorCode:
530, errorText:Failed to create load balancer rule: SSH
> In the management server logs:
> WARN  [network.lb.LoadBalancingRulesManagerImpl] (1347080201@qtp-675153853-0:) Failed
to create load balancer due to 
> com.cloud.exception.InvalidParameterValueException: Scheme Public is not supported by
the network offering [Network Offering [14-Guest-VPC Network offering-P5GNGX]
> 	at com.cloud.network.lb.LoadBalancingRulesManagerImpl.isLbServiceSupportedInNetwork(LoadBalancingRulesManagerImpl.java:2103)
> 	at com.cloud.network.lb.LoadBalancingRulesManagerImpl.createPublicLoadBalancer(LoadBalancingRulesManagerImpl.java:1401)
> 	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> 	at com.cloud.network.lb.LoadBalancingRulesManagerImpl.createPublicLoadBalancerRule(LoadBalancingRulesManagerImpl.java:1329)
> 	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> 	at org.apache.cloudstack.api.command.user.loadbalancer.CreateLoadBalancerRuleCmd.create(CreateLoadBalancerRuleCmd.java:281)
> 	at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:101)
> 	at com.cloud.api.ApiServer.queueCommand(ApiServer.java:475)
> 	at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
> 	at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
> 	at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
> 	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> 	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> 	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:326)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> ERROR [cloud.api.ApiServer] (1347080201@qtp-675153853-0:) unhandled exception executing
api command: createLoadBalancerRule
> com.cloud.utils.exception.CloudRuntimeException: Failed to create load balancer rule:
SSH
> 	at com.cloud.network.lb.LoadBalancingRulesManagerImpl.createPublicLoadBalancerRule(LoadBalancingRulesManagerImpl.java:1350)
> 	at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> 	at org.apache.cloudstack.api.command.user.loadbalancer.CreateLoadBalancerRuleCmd.create(CreateLoadBalancerRuleCmd.java:281)
> 	at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:101)
> 	at com.cloud.api.ApiServer.queueCommand(ApiServer.java:475)
> 	at com.cloud.api.ApiServer.handleRequest(ApiServer.java:371)
> 	at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
> 	at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> 	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401)
> 	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
> 	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> 	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:326)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:928)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410)
> 	at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)

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