You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sheng Yang (JIRA)" <ji...@apache.org> on 2013/06/21 19:07:19 UTC
[jira] [Resolved] (CLOUDSTACK-1440) Baremetal - Destroy VM fail due
to com.cloud.exception.OperationTimedoutException
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sheng Yang resolved CLOUDSTACK-1440.
------------------------------------
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 <sh...@citrix.com>
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 - Destroy VM fail due to com.cloud.exception.OperationTimedoutException
> -----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1440
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1440
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: MS rhel6.3 ASF 4.1 latest build 2/26/13
> host baremetal
> Reporter: angeline shen
> Assignee: Sheng Yang
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz, Screenshot-CloudStack - Mozilla Firefox.png
>
>
> 1. create basic zone baremetal type. Add DHCP PXE server. Add baremetal host, template
> Deploy VM
> 2. Destroy VM. VM remain in Stopping state for over 30 minutes. Then it timed out & VM returned to
> running state again.
--
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