[
https://issues.apache.org/jira/browse/CLOUDSTACK-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642427#comment-13642427
]
Alena Prokharchyk commented on CLOUDSTACK-2195:
-----------------------------------------------
The "return false" event in finally() block overrode the CloudRuntimeException
you've been throwing, thats why the exception was never propagated to the
caller stack
(http://stackoverflow.com/questions/48088/returning-from-a-finally-block-in-java)
You should apply fix suggested by Edison - the real problem was, the
UserVmManagerImpl.stopVirtualMachine call was never checking the result of the
vmEntity.stop call.
> stopVirtualMachine reports success when agent can't be reached
> --------------------------------------------------------------
>
> Key: CLOUDSTACK-2195
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2195
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: management server talking to a KVM host
> Reporter: Marcus Sorensen
> Priority: Critical
> Fix For: 4.1.0
>
>
> 1. deploy, start a VM
> 2. stop KVM agent where VM is running
> 3. attempt to stopVirtualMachine
> Notice that the job response indicates success. The state, however, remains
> 'running'
--
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
