Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Fri, 1 Mar 2013 02:19:12 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-dev@incubator.apache.org
Message-ID: <JIRA.12610203.1349337616138.362661.1362104352546@arcas>
In-Reply-To: <JIRA.12610203.1349337616138@arcas>
References: <JIRA.12610203.1349337616138@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-255) Null pointer exception while
 creating portforwarding rule after performing UpdateNetworkCmd
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Animesh Chaturvedi commented on CLOUDSTACK-255:
-----------------------------------------------

Vijay, please check if this is still an issue? Seems to have been open for a long time
                
> Null pointer exception while creating portforwarding rule after performing UpdateNetworkCmd 
> --------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-255
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-255
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: pre-4.0.0
>            Reporter: Sailaja Mada
>            Assignee: Venkata Siva Vijayendra Bhamidipati
>            Priority: Critical
>             Fix For: 4.1.0
>
>         Attachments: api-server.log, management-server-pf.log
>
>
> Steps :
> 1. Install and Configure Advanced Zone using VMWARE ESXi 5 server.
> 2. Create new account 
> 3. Create Network offering1  with Redundant Router enabled , 
> Supported Services: Vpn, PortForwarding, SourceNat, Firewall, UserData, Dns, Lb, Dhcp, StaticNat
> Service Capabilities	SupportedSourceNatTypes: peraccount, RedundantRouter: true, SupportedLBIsolation: dedicated, ElasticLb: false, ElasticIp: false
> 4. Create Network with the above offering. 
> 5. Deploy instance with this network
> 6. Both Routers and instance got deployed. 
> 7.  Configure LB rule with 22  port , Enable VPN , Once the key is generated , disable VPN 
> 8. Create Network offering 2 with Single Router and 
> Supported Services	PortForwarding, SourceNat, Firewall, Dns, Dhcp
> Service Capabilities	SupportedSourceNatTypes: peraccount, RedundantRouter: false
> 9. Edit Network details and update the Network offering 1 to Network offering 2.
> 10.It created new Router and deleted Redundant Routers. LB Rules are not deleted.  
> 11. Now tried to create Port forwarding Rule with 22 . 
> Observation: 
> It failed with Null Pointer exception :
> 2012-10-04 13:17:20,372 ERROR [cloud.api.ApiDispatcher] (catalina-exec-1:null) Exception while executing CreatePortForwardingRuleCmd:
> java.lang.NullPointerException
>         at com.cloud.network.NetworkManagerImpl.canIpUsedForService(NetworkManagerImpl.java:863)
>         at com.cloud.network.NetworkManagerImpl.checkIpForService(NetworkManagerImpl.java:6895)
>         at com.cloud.network.rules.RulesManagerImpl.createPortForwardingRule(RulesManagerImpl.java:205)
>         at com.cloud.utils.component.ComponentLocator$InterceptorDispatcher.intercept(ComponentLocator.java:1231)
>         at com.cloud.api.commands.CreatePortForwardingRuleCmd.create(CreatePortForwardingRuleCmd.java:299)
>         at com.cloud.api.ApiDispatcher.dispatchCreateCmd(ApiDispatcher.java:84)
>         at com.cloud.api.ApiServer.queueCommand(ApiServer.java:484)
>         at com.cloud.api.ApiServer.handleRequest(ApiServer.java:422)
>         at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:304)
>         at com.cloud.api.ApiServlet.doGet(ApiServlet.java:63)
>         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)
> 2012-10-04 13:17:21,003 DEBUG [agent.manager.AgentManagerImpl] (AgentManager-Handler-7:null) Ping from 4
> Fire bug log:
> "NetworkError: 530  - http://10.102.125.211:8080/client/api?command=createPortForwardingRule&response=json&sessionkey=aH06kOV%2BeNBJojMmNF3HYNy6NJ4%3D&ipaddressid=f3c2bc15-365e-48db-98fd-a720a7dc331b&privateport=80&publicport=80&protocol=tcp&virtualmachineid=fcb14ef4-0a21-4b26-96c1-4b539a2987c9&openfirewall=false&networkid=79b683d1-7306-4769-b95e-7cef7abf5c33&_=1349336891753"
> { "createportforwardingruleresponse" : {"uuidList":[],"errorcode":530} }

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