You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/04/19 20:11:15 UTC
[jira] [Commented] (CLOUDSTACK-2105) [Dedicated Resources : Public
IP Addresses per tenant]NPE on releasing IP from an account which has VPCs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636676#comment-13636676 ]
ASF subversion and git services commented on CLOUDSTACK-2105:
-------------------------------------------------------------
Commit 8d8a0ebe109ae6e9896caee945e29fd8ac778d2c in branch refs/heads/master from [~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8d8a0eb ]
CLOUDSTACK-2105.
While releasing an IP range from an acount if any of the Public IPs in the range is a source nat ip then the IP is not disassociated.
During the check CS also checks if the network the IP is associted with is not null. This results in an NPE for an account that has VPC s
because the public IP of a VPC domain router is common to all VPC tiers and not associated with a network
Remove the check to find the network associted with a source nat IP for both ReleasePublicIpRange and DeleteVlanPublicIpRange
> [Dedicated Resources : Public IP Addresses per tenant]NPE on releasing IP from an account which has VPCs
> --------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2105
> 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
> Reporter: Abhinav Roy
> Assignee: Likitha Shetty
> Priority: Critical
> Fix For: 4.2.0
>
>
> Steps :
> ===============================
> 1. Deploy an advanced networking setup and create an account A1
> 2. Now dedicate an IP range R1 to this account A1
> 3. Login to account A1 and create a VPC
> 4. Release the IP range allocated to A1
> Expected behaviour :
> ===============================
> 1. All the steps should be successful, the IP range should be released without any issue.
> Observed behaviour :
> ===============================
> 1. When we try to release IP Range from an account which has VPC then we get a NPE
> 2013-04-19 11:03:42,428 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null) ===START=== 10.144.6.35 -- GET command=releasePublicIpRange&response=json&sessionkey=sQDW3X9W%2FSmHgWtniEgzMl3Wrxo%3D&id=f24eeee0-5b93-4b8b-979d-1d3d95787a66&_=1366349693799
> 2013-04-19 11:03:42,434 DEBUG [cloud.configuration.ConfigurationManagerImpl] (catalina-exec-14:null) lock vlan 9 is acquired
> 2013-04-19 11:03:42,441 ERROR [cloud.api.ApiServer] (catalina-exec-14:null) unhandled exception executing api command: releasePublicIpRange
> java.lang.NullPointerException
> at com.cloud.configuration.ConfigurationManagerImpl.releasePublicIpRange(ConfigurationManagerImpl.java:2805)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at com.cloud.configuration.ConfigurationManagerImpl.releasePublicIpRange(ConfigurationManagerImpl.java:2776)
> at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> at org.apache.cloudstack.api.command.admin.vlan.ReleasePublicIpRangeCmd.execute(ReleasePublicIpRangeCmd.java:69)
> at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:164)
> at com.cloud.api.ApiServer.queueCommand(ApiServer.java:454)
> at com.cloud.api.ApiServer.handleRequest(ApiServer.java:304)
> at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:302)
> at com.cloud.api.ApiServlet.doGet(ApiServlet.java:66)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:555)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:889)
> at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:721)
> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:2268)
> 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)
> 2013-04-19 11:03:42,444 DEBUG [cloud.api.ApiServlet] (catalina-exec-14:null) ===END=== 10.144.6.35 -- GET command=releasePublicIpRange&response=json&sessionkey=sQDW3X9W%2FSmHgWtniEgzMl3Wrxo%3D&id=f24eeee0-5b93-4b8b-979d-1d3d95787a66&_=1366349693799
--
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