You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sudha Ponnaganti (JIRA)" <ji...@apache.org> on 2013/06/17 21:42:20 UTC
[jira] [Updated] (CLOUDSTACK-3000) [Automation] Router not stopped
based on "network.gc.interval" property
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sudha Ponnaganti updated CLOUDSTACK-3000:
-----------------------------------------
Priority: Blocker (was: Major)
> [Automation] Router not stopped based on "network.gc.interval" property
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3000
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3000
> 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: Automation Env
> Master build
> Reporter: Rayees Namathponnan
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Step 1 : Create advanced zone
> Step 2: set network.gc.interval = 60, in global properties
> Step 3 : Create an account, deploy and deploy vm with new network
> Step 4 : Stop VM
> Expected Result
> Router should be stopped after one minute vm stops, but router taking more than 2 minute to stop
> Please see the below log
> a) VM i-141-163-QA stop command send at 14 01:35:03,
> b) i-141-163-QA stopped at 01:35:32
> c ) Router r-164-QA should be stopped at 1:36:32 but, router stop command issues at 01:37:47
> 2013-06-14 01:35:03,634 DEBUG [cloud.api.ApiDispatcher] (Job-Executor-28:job-624) ControlledEntity name is:com.cloud.network.router.VirtualRouter
> 2013-06-14 01:35:03,663 DEBUG [cloud.capacity.CapacityManagerImpl] (Job-Executor-28:job-624) VM state transitted from :Running to Stopping with event: StopRequestedvm's origin
> al host id: 4 new host id: 4 host id before state transition: 4
> 2013-06-14 01:35:03,666 DEBUG [agent.transport.Request] (Job-Executor-28:job-624) Seq 4-524091527: Sending { Cmd , MgmtId: 29066118877352, via: 4, Ver: v1, Flags: 100111, [{"
> StopCommand":{"isProxy":false,"vmName":"i-141-163-QA","wait":0}}] }
> 2013-06-14 01:35:04,908 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:null) ===START=== 10.216.51.168 -- GET command=listVirtualMachines&response=json&sessionkey=dQ8vH3fJP0
> MSmEE61n6FIRSKDOA%3D&listAll=true&page=1&pagesize=20&_=1371188260986
> 2013-06-14 01:35:04,922 DEBUG [cloud.api.ApiServlet] (catalina-exec-12:nu
> 2013-06-14 01:35:32,311 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-28:job-624) Complete async job-624, jobStatus: 1, resultCode: 0, result: org.apache.cloudstack.api.response.UserVmResponse@30c871f
> 2013-06-14 01:35:32,336 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-28:job-624) Done executing org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-624
> 2013-06-14 01:35:33,674 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null) ===START=== 10.216.51.168 -- GET command=queryAsyncJobResult&jobId=63e1a985-93f5-4f1b-9763-6f147cdd34e8&response=json&sessionkey=dQ8vH3fJP0MSmEE61n6FIRSKDOA%3D&_=1371188289775
> 2013-06-14 01:35:33,683 DEBUG [cloud.async.AsyncJobManagerImpl] (catalina-exec-25:null) Async job-624 completed
> 2013-06-14 01:35:33,689 DEBUG [cloud.api.ApiServlet] (catalina-exec-25:null) ===END=== 10.216.51.168 -- GET command=queryAsyncJobResult&jobId=63e1a985-93f5-4f1b-9763-6f147cdd34e8&response=json&sessionkey=dQ8vH3fJP0MSmEE61n6FIRSKDOA%3D&_=1371188289775
> 2013-06-14 01:37:47,793 DEBUG [cloud.network.NetworkManagerImpl] (Network-Scavenger-1:null) Sending network shutdown to VirtualRouter
> 2013-06-14 01:37:47,795 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (Network-Scavenger-1:null) Stopping router VM[DomainRouter|r-164-QA]
> 2013-06-14 01:37:47,801 DEBUG [cloud.capacity.CapacityManagerImpl] (Network-Scavenger-1:null) VM state transitted from :Running to Stopping with event: StopRequestedvm's origi
> nal host id: 4 new host id: 4 host id before state transition: 4
--
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