Red Hat Bugzilla – Bug 1298193
Retire vm doesn't work on Azure cloud provider
Last modified: 2016-08-02 21:33:42 EDT
Created attachment 1114397 [details]
Azure retire vm
Description of problem:
When you retire vm on azure provider the power state of vm should be off/stopped what means that vm isn't running, however only the status of vm is change to retired. Please take a look at screenshot.
Also, I'll attach emv and automation log files.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set up Azure cloud provider
2. Open any virtual machine
3. Press Lifecycle -> Retire this VM
5. Wait a little bit and check the status of vm and power state
The status of vm is Retired but power state is on
The power state of vm should be off, also cfme shouldn't allow vm to start/power on
The vm navigation tree update status of vm after reload, so please press on "All VMs & Templates" to update statuses.
IP is 10.8.59.182
The vm name is testvmretire
This vm was create only for this test, so you can do whatever you need with this vm.
Created attachment 1114398 [details]
Created attachment 1114399 [details]
The failure is likely caused by the missing method reported in https://bugzilla.redhat.com/show_bug.cgi?id=1291274. Can you take a look and ported the PR to downstream. Please check with Tina.
I can't access your appliance. Can you make this available for me?
Use this one for 18.104.22.168 It's configured already.
The generic pre_retirement method is missing.
We are working on a fix now.
This issue has been resolved: https://github.com/ManageIQ/manageiq/pull/5779
This is verified as working. I've terminated or otherwise retired 10 different instances without any issues.
Tested on 22.214.171.124 Beta on on https://10.16.7.174/vm_cloud/explorer
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.