You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Wei Zhou (JIRA)" <ji...@apache.org> on 2013/07/23 14:12:49 UTC
[jira] [Commented] (CLOUDSTACK-3734) VMs will be stopped on
Devcloud after second run
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716338#comment-13716338 ]
Wei Zhou commented on CLOUDSTACK-3734:
--------------------------------------
please notice the following logs
2013-07-23 13:57:04,000 INFO [cloud.vm.VirtualMachineManagerImpl] (AgentTaskPool-1:ctx-28ff2778) Found vm i-2-3-VM in inconsistent state. Running on CS while Stopped on agent
2013-07-23 13:57:04,028 DEBUG [cloud.vm.VirtualMachineManagerImpl] (AgentTaskPool-1:ctx-28ff2778) VM i-2-3-VM: cs state = Running and realState = Stopped
2013-07-23 13:57:04,028 DEBUG [cloud.vm.VirtualMachineManagerImpl] (AgentTaskPool-1:ctx-28ff2778) VM i-2-3-VM: cs state = Running and realState = Stopped
2013-07-23 13:57:04,028 DEBUG [cloud.ha.HighAvailabilityManagerImpl] (AgentTaskPool-1:ctx-28ff2778) VM does not require investigation so I'm marking it as Stopped: VM[User|wei001]
2013-07-23 13:57:04,029 WARN [apache.cloudstack.alerts] (AgentTaskPool-1:ctx-28ff2778) alertType:: 8 // dataCenterId:: 1 // podId:: 1 // clusterId:: null // message:: VM (name: wei001, id: 3) stopped unexpectedly on host id:1, availability zone id:1, pod id:1
2013-07-23 13:57:04,046 DEBUG [cloud.ha.HighAvailabilityManagerImpl] (AgentTaskPool-1:ctx-28ff2778) VM is not HA enabled so we're done.
2013-07-23 13:57:04,072 DEBUG [cloud.capacity.CapacityManagerImpl] (AgentTaskPool-1:ctx-28ff2778) VM state transitted from :Running to Stopping with event: StopRequestedvm's original host id: 1 new host id: 1 host id before state transition: 1
2013-07-23 13:57:04,082 DEBUG [agent.transport.Request] (AgentTaskPool-1:ctx-28ff2778) Seq 1-125108228: Sending { Cmd , MgmtId: 8796757665554, via: 1, Ver: v1, Flags: 100011, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-3-VM","wait":0}}] }
2013-07-23 13:57:04,083 DEBUG [agent.transport.Request] (AgentTaskPool-1:ctx-28ff2778) Seq 1-125108228: Executing: { Cmd , MgmtId: 8796757665554, via: 1, Ver: v1, Flags: 100011, [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"vmName":"i-2-3-VM","wait":0}}] }
2013-07-23 13:57:04,083 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-1:null) Seq 1-125108228: Executing request
2013-07-23 13:57:04,212 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-1:null) 9. The VM i-2-3-VM is in Stopping state
> VMs will be stopped on Devcloud after second run
> ------------------------------------------------
>
> Key: CLOUDSTACK-3734
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3734
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Reporter: Wei Zhou
> Attachments: test.log
>
>
> on Devcloud
> The first time "mvn -pl :cloud-client-ui jetty:run" works well.
> When I use CTRL+C to stop it and run again.
> The existing VMs will stop, and the virtual routers will stopp as well.
> This issue appeared after commit 541f9d7f, and still existing in master branch.
> logs in vmops.log
--
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