[ https://issues.apache.org/jira/browse/CLOUDSTACK-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664673#comment-13664673 ]
Alena Prokharchyk commented on CLOUDSTACK-2632: ----------------------------------------------- Related to pVlan functionality. > [Automation] Failed to stop VR with null pointer exception > ----------------------------------------------------------- > > Key: CLOUDSTACK-2632 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2632 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Network Controller > Affects Versions: 4.2.0 > Environment: VMware > Master branch build (4.2.0) > Reporter: Rayees Namathponnan > Priority: Blocker > Fix For: 4.2.0 > > > This issue is observed in automation VMare environment > Steps to reproduce > Step 1 : Create an account > Step 2 : login to account and create a VM > Step 3 : Delete the account > VR always shows in stoping state, and null pointer error exception > pAnswer } } > 2013-05-22 15:50:15,283 DEBUG [agent.manager.AgentAttache] > (DirectAgent-236:null) Seq 4-826868349: No more commands found > 2013-05-22 15:50:15,283 DEBUG > [network.router.VirtualNetworkApplianceManagerImpl] (AccountChecker-1:null) > Successfully updated user statistics as a part of domR > VM[DomainRouter|r-127-QA] reboot/stop > 2013-05-22 15:50:15,288 WARN [cloud.network.NetworkManagerImpl] > (AccountChecker-1:null) Unable to complete shutdown of the network elements > due to element: VirtualRouter > java.lang.NullPointerException > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.finalizeStop(VirtualNetworkApplianceManagerImpl.java:2612) > at > com.cloud.network.router.VpcVirtualNetworkApplianceManagerImpl.finalizeStop(VpcVirtualNetworkApplianceManagerImpl.java:1396) > at > com.cloud.vm.VirtualMachineManagerImpl.advanceStop(VirtualMachineManagerImpl.java:1179) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:2741) > at > com.cloud.network.router.VirtualNetworkApplianceManagerImpl.stop(VirtualNetworkApplianceManagerImpl.java:258) > at > com.cloud.network.element.VirtualRouterElement.shutdown(VirtualRouterElement.java:657) > at > com.cloud.network.NetworkManagerImpl.shutdownNetworkElementsAndResources(NetworkManagerImpl.java:2625) > at > com.cloud.network.NetworkManagerImpl.shutdownNetwork(NetworkManagerImpl.java:2555) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.network.NetworkManagerImpl.destroyNetwork(NetworkManagerImpl.java:2684) > at > com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125) > at > com.cloud.user.AccountManagerImpl.cleanupAccount(AccountManagerImpl.java:655) > at > com.cloud.user.AccountManagerImpl$AccountCleanupTask.run(AccountManagerImpl.java:1460) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > 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:722) > 2013-05-22 15:50:15,294 DEBUG [cloud.network.NetworkManagerImpl] > (AccountChecker-1:null) Network is not not in the correct state to be > destroyed: Implemented > 2013-05-22 15:50:15,294 WARN [cloud.user.AccountManagerImpl] > (AccountChecker-1:null) Unable to destroy network Ntwk[278|Guest|8] as a part > of account id=115 cleanup. -- 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