[
https://issues.apache.org/jira/browse/CLOUDSTACK-9451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435217#comment-15435217
]
ASF GitHub Bot commented on CLOUDSTACK-9451:
--------------------------------------------
Github user kiwiflyer commented on the issue:
https://github.com/apache/cloudstack/pull/1635
@ProjectMoon Jeff, could you help review this, as I believe you were the
first to point it out on the list.
From talking to Nathan, it sounds like we're not sure KVM is actually
affected by this bug. He was in the process of doing some digging. Regardless
of that, it probably affects other hypervisors.
> stopVirtualMachine ignores forced parameter
> -------------------------------------------
>
> Key: CLOUDSTACK-9451
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9451
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API, Management Server
> Affects Versions: 4.8.0, 4.9.0
> Reporter: Nathan Johnson
> Priority: Minor
>
> As reported by Jeff Hair from the mailing list:
> Hi,
> I'm looking at the documentation and then the code for stopVirtualMachine.
> The forced parameter is passed down into the VM manager, where it seems to
> be ignored. This means that cleanupEvenIfFailed during VM stop will always
> be false, despite what the API command says. Going back to commit a4f4c986
> in 2013, we can see that the forced parameter was used. During subsequent
> refactoring, this seems to have vanished.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
