Description of problem: Azure supports two automation modes for Stopping a VM. Stopped is effectively Paused. The machine resources are still available and it is still incurring charges as if it were running. However, in the Azure Portal, when you select a VM and click Stop, it performs the Stopped(Deallocated) command which is the same thing as going into the VM and choosing Shutdown. When I select CloudForms Power:Stop on a running Azure VM, is sends the first stopped. But if I go to that VM in the Portal, the Stop option is still available, and the VM is still costing me money. There is a better description of the differences here: https://blogs.technet.microsoft.com/uspartner_ts2team/2014/10/10/azure-virtual-machines-stopping-versus-stopping-deallocating/ I can't say it's busted, but unless we provide both options in the Power menu, I would suggest we use the same behavior as the Azure portal. As always, I'm open to further discussions. Version-Release number of selected component (if applicable): 5.6 How reproducible: Always Steps to Reproduce: 1. In CF, select an Azure VM and choose Stop from the Power Dropdown 2. Go to Azure Portal, select VM and choose Stop. 3. Actual results: I would think we should copy the same behavior as if the user were in Azure. Expected results: Additional info:
This is not a 5.6 regression. 5.5 worked the same way although I didn't notice until my account got locked out for exceeding charges limit.
Ok, how about "stop" for deallocation and "suspend" (or "pause") for just a power off?
Do it.
PR submitted: https://github.com/ManageIQ/manageiq/pull/8152
This works. Tested 5605 using https://10.16.6.211/vm_cloud/explorer# Moving to Verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1348