cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9451) stopVirtualMachine ignores forced parameter
Date Thu, 11 Aug 2016 12:55:20 GMT


ASF GitHub Bot commented on CLOUDSTACK-9451:

GitHub user nathanejohnson opened a pull request:

    Re-doing against 4.8 since this is a bug, not a feature.

You can merge this pull request into a Git repository by running:

    $ git pull feature/honor_force_stop_vm

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1635
commit d5471b94e7617565836c1460007cbf6afa4c12ec
Author: Nathan Johnson <>
Date:   2016-08-11T12:52:05Z

    Re-doing against 4.8 since this is a bug, not a feature.


> stopVirtualMachine ignores forced parameter
> -------------------------------------------
>                 Key: CLOUDSTACK-9451
>                 URL:
>             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

View raw message