[
https://issues.apache.org/jira/browse/CLOUDSTACK-5928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879261#comment-13879261
]
ASF subversion and git services commented on CLOUDSTACK-5928:
-------------------------------------------------------------
Commit 29e44b1b67fa1dcc8289f15b6ed82fa9edb88c7b in branch
refs/heads/4.3-forward from [~kelveny]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=29e44b1 ]
CLOUDSTACK-5928: Use legacy vmsync logic by default
> [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
> 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.1.5#6160)
