[ https://issues.apache.org/jira/browse/CLOUDSTACK-9451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15695120#comment-15695120 ]
ASF subversion and git services commented on CLOUDSTACK-9451: ------------------------------------------------------------- Commit 5811d33658fe1651e43dcca67c35c712f9ba4107 in cloudstack's branch refs/heads/master from [~rohit.ya...@shapeblue.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5811d33 ] Merge pull request #1635 from myENA/feature/honor_force_stop_vm CLOUDSTACK-9451https://issues.apache.org/jira/browse/CLOUDSTACK-9451 Re-doing against 4.8 since this is a bug, not a feature. * pr/1635: CLOUDSTACK-9451 Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com> > 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)