[
https://issues.apache.org/jira/browse/CLOUDSTACK-8103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255505#comment-14255505
]
ASF subversion and git services commented on CLOUDSTACK-8103:
-------------------------------------------------------------
Commit 788fe5a27365e57508e0c1c967da46da0314e3e4 in cloudstack's branch
refs/heads/4.5 from [~koushikd]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=788fe5a ]
CLOUDSTACK-8103: Vmsync marks VM as stopped even after failing to stop it in HV
During vmsync if StopCommand (issued as part of PowerOff/PowerMissing report)
fails to stop VM (since VM is running on HV),
don't transition VM state to "Stopped" in CS db. Also added a check to throw
ConcurrentOperationException if vm state is not
"Running" after start operation.
> Vmsync marks VM as stopped even after failing to stop it in HV
> --------------------------------------------------------------
>
> Key: CLOUDSTACK-8103
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8103
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.5.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Priority: Critical
> Fix For: 4.5.0
>
>
> Vmsync reports poweroff/powermissing and tries to stop vm. The stop agent
> command fails as it finds VM to be running in HV. Even though stop command
> fails, the VM is marked as stopped in the database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
