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 Mon, 29 Aug 2016 08:17:20 GMT


ASF GitHub Bot commented on CLOUDSTACK-9451:

Github user rhtyd commented on a diff in the pull request:
    --- Diff: engine/api/src/org/apache/cloudstack/engine/cloud/entity/api/
    @@ -115,6 +115,12 @@ String reserve(DeploymentPlanner plannerToUse, @BeanParam DeploymentPlan
plan, E
         boolean stop(String caller) throws ResourceUnavailableException, CloudException;
    +     * Stop the virtual machine, optionally force
    +     *
    +     */
    +    boolean stop(String caller, boolean forced) throws ResourceUnavailableException,
    --- End diff --
    @jburwell the `forced` flag has always existed, the `stopVirtualMachine` API accepts this
and the query layer too has a method with this signature (
but it does not honour or pass this flag to the layers below, so effectively stopVM API with/without
the `forced` flag has the same effect.

> 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