You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kelven Yang (JIRA)" <ji...@apache.org> on 2014/05/07 01:36:26 UTC
[jira] [Resolved] (CLOUDSTACK-5928) [VM Sync] - Vmware - When a Vm
is "suspended" from outside of CloudStack , this results in CS stopping the
VM.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kelven Yang resolved CLOUDSTACK-5928.
-------------------------------------
Resolution: Fixed
> [VM Sync] - Vmware - When a Vm is "suspended" from outside of CloudStack , this results in CS stopping the VM.
> --------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5928
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5928
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Environment: Latest build from 4.3
> Reporter: Sangeetha Hariharan
> Assignee: Kelven Yang
> Priority: Critical
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> [VM Sync] - Vmware - When a Vm is "suspended" from outside of CloudStack , this results in CS stopping the VM
> PreReq:
> Have few Vms deployed using Cloudstack.
> Steps:
> Outside of Cloudstack , Suspend an existing VM that is in "Running" state.
> CloudStack is stopping this VM when VM state is reported.
> Expected Behavior:
> If CP does not handle "suspend" state , we should leave the VM in "Running" state. We should not be stopping the VM.
--
This message was sent by Atlassian JIRA
(v6.2#6252)