You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Venkata Siva Vijayendra Bhamidipati (JIRA)" <ji...@apache.org> on 2013/07/18 00:34:49 UTC
[jira] [Closed] (CLOUDSTACK-2969) Exception when creating vlan ip
range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Venkata Siva Vijayendra Bhamidipati closed CLOUDSTACK-2969.
-----------------------------------------------------------
Verified.
> Exception when creating vlan ip range
> -------------------------------------
>
> Key: CLOUDSTACK-2969
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2969
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: vmware deployment in cloudstack
> Reporter: Venkata Siva Vijayendra Bhamidipati
> Assignee: Venkata Siva Vijayendra Bhamidipati
> Labels: automation, integration-tests
> Fix For: 4.2.0
>
>
> When creating an advanced zone configuration in the GUI using the zone config wizard, this exception is encountered:
> 135&endIp=10.223.74.165&response=json&sessionkey=Uc2mmfyGUdrKCo7hDfiTMEwk8sU%3D&_=1371065885754
> 2013-06-12 06:14:29,530 DEBUG [cloud.api.ApiServlet] (324500051@qtp-2127994111-6:null) ===START=== 10.217.252.54 -- GET command=createVlanIpRange&zoneId=3bc75416-c576-4456-8e38-0cabc0f4ee3e&vlan=541&gateway=10.223.154.129&netmask=255.255.255.128&startip=10.223.154.135&endip=10.223.154.165&forVirtualNetwork=true&response=json&sessionkey=Uc2mmfyGUdrKCo7hDfiTMEwk8sU%3D&_=1371065885983
> 2013-06-12 06:14:29,577 ERROR [cloud.api.ApiServer] (324500051@qtp-2127994111-6:null) unhandled exception executing api command: createVlanIpRange
> java.lang.NullPointerException
> at com.cloud.configuration.ConfigurationManagerImpl.createVlanAndPublicIpRange(ConfigurationManagerImpl.java:2531)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at org.apache.cloudstack.api.command.admin.vlan.CreateVlanIpRangeCmd.execute(CreateVlanIpRangeCmd.java:211)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:528)
> 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