Abhinav Roy created CLOUDSTACK-84:
-------------------------------------

             Summary: Getting Null Pointer Excpetion while executing 
listRouters command after deleting a user project.
                 Key: CLOUDSTACK-84
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-84
             Project: CloudStack
          Issue Type: Bug
          Components: Network Controller
    Affects Versions: pre-4.0.0
         Environment: Management sever : Rhel 6.3
Setup : Advanced
Host : XenServer 6.0.2
Build Details :-
Git Revision: 03df2fa9dd45c938f72cd1866044b09d1b0cc978
Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git

            Reporter: Abhinav Roy
             Fix For: pre-4.0.0


Steps to reproduce :
-------------------------
1. Deploy a CS advanced networking setup.
2. create a sub-domain 'Domain1' under 'ROOT' domain.
3. Create 2 users - user1 and user2 under 'Domain1'.
4. login as user1 and create a project. Add user2 to the project.
5. Create 2 VMs , one as user1 and the other as user2.
6. Login as user1(project admin) and delete the project.


Expected Behaviour :
------------------------------
The project deletion along with deletion of all the resources associated with 
the project should be successful and no error should be seen.

Observed Behaviour :
------------------------------
1. The project deletion was successful and all resources associated with the 
project were released or deleted appropriately (accounts were released, VMs 
were deleted)

2. After the deletion was done, when I tried to list the virtual routers, i got 
the following Null pointer exception


Exception while executing ListRoutersCmd:
java.lang.NullPointerException
        at 
com.cloud.api.ApiResponseHelper.populateOwner(ApiResponseHelper.java:3362)
        at 
com.cloud.api.ApiResponseHelper.createDomainRouterResponse(ApiResponseHelper.java:1771)
        at 
com.cloud.api.commands.ListRoutersCmd.execute(ListRoutersCmd.java:136)
        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:138)
        at com.cloud.api.ApiServer.queueCommand(ApiServer.java:543)
        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) 

3. In UI also we are not able to see the routers on the virtual routers page.
4. The issue persists even after restarting Management Server.



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

Reply via email to