[
https://issues.apache.org/jira/browse/CLOUDSTACK-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sheng Yang resolved CLOUDSTACK-1618.
------------------------------------
Resolution: Fixed
Don't know if it's a real bug, but as long as I tested the following commit,
it's fine:
commit a6a49490fbcc344f8a37d8c2ef0254da3ae39d89
Author: Sheng Yang <[email protected]>
Date: Tue Jun 18 14:04:05 2013 -0700
Fix baremetal functionality
1. Baremetal doesn't have secondary storage, so we don't need check them.
2. The new "AddBaremetalHostCmd" hasn't been used by UI, so keep the
validity
checking out for now. "AddHostCmd" would still works.
3. Baremetal haven't implemented multiple ip range feature(CLOUDSTACK-702),
return true for now for single range.
> Baremetal - Stop VM fail
> ------------------------
>
> Key: CLOUDSTACK-1618
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1618
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Baremetal, Management Server
> Affects Versions: 4.2.0
> Environment: MS ASF 4.1 build 70
> host baremetal guest OS centos 6.3
> Reporter: angeline shen
> Assignee: Sheng Yang
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz
>
>
> 1. create basic zone baremetal network type. Add DHCP PXE server. Add
> baremetal host, template centos 6.3. Deploy VM with baremetal template
> centos 6.3
> 2.Stop VM . VM was not stopped. After 30 minutes, Timed out . Unable to
> stop vm VM[User|z1centos63V1]
> 2013-03-08 20:21:00,814 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-28:job-28) Executing
> org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-28
> 2013-03-08 20:21:00,815 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null)
> ===END=== 10.216.133.70 -- GET
> command=stopVirtualMachine&id=562e36e8-36ec-4d0b-8341-ff869bb0483d&forced=true&response=json&sessionkey=kQqK9pFlb8STco
> ZbZ%2BOqzBtxXng%3D&_=1362792722106
> 2013-03-08 20:51:00,847 DEBUG [agent.manager.AgentAttache]
> (Job-Executor-28:job-28) Seq 1-51445943: Waited too long.
> 2013-03-08 20:51:00,847 INFO [utils.exception.CSExceptionErrorCode]
> (Job-Executor-28:job-28) Could not find exception:
> com.cloud.exception.OperationTimedoutException in error code list for
> exceptions
> 2013-03-08 20:51:00,847 WARN [agent.manager.AgentAttache]
> (Job-Executor-28:job-28) Seq 1-51445943: Timed out on Seq 1-51445943: { Cmd
> , MgmtId: 206915885079873, via: 1, Ver: v1, Flags: 100111,
> [{"StopCommand":{"isProxy":false
> ,"vmName":"i-2-1-VM","wait":0}}] }
> 2013-03-08 20:51:00,847 DEBUG [agent.manager.AgentAttache]
> (Job-Executor-28:job-28) Seq 1-51445943: Cancelling.
> 2013-03-08 20:51:00,847 WARN [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-28:job-28) Unable to stop vm VM[User|z1centos63V1]
> 2013-03-08 20:51:00,902 DEBUG [cloud.capacity.CapacityManagerImpl]
> (Job-Executor-28:job-28) VM state transitted from :Stopping to Running with
> event: OperationFailedvm's original host id: 1 new host id: 1 host id before
> state t
> ransition: 1
> 2013-03-08 20:51:00,909 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-28:job-28) Complete async job-28, jobStatus: 1, resultCode: 0,
> result: org.apache.cloudstack.api.response.UserVmResponse@b95ab39
> 2013-03-08 20:51:00,930 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-28:job-28) Done executing
> org.apache.cloudstack.api.command.user.vm.StopVMCmd for job-28
> 2013-03-08 20:51:01,742 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
> ===START=== 10.216.133.70 -- GET
> command=queryAsyncJobResult&jobId=1043a559-426d-4471-942d-59a56ce40793&response=json&sessionkey=kQqK9pFlb8STcoZbZ%2B
> OqzBtxXng%3D&_=1362794523111
> 2013-03-08 20:51:01,751 DEBUG [cloud.async.AsyncJobManagerImpl]
> (catalina-exec-5:null) Async job-28 completed
--
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
