Description of problem: you cannot triger retirement via an API call; service retirement can be trigger it via an API call and can result in the retirement of a VM, however without a service one would need to instantiate an automate model and interact with the automate APIs in order to directly retire a VM. Version-Release number of selected component (if applicable): cfme-5.5.2.4-1.el7cf.x86_64 Additional info: this bug is requesting that there be an API created that allows one to trigger retirement by interacting with a VM object
Colin, You can retire a vm with the following API call: POST /api/vms/:id { "action": "retire" } Please let me know if that doesn't meet your needs. Thanks, Tim
This looks like what we would like. Thanks for the info.
Tim/Colin, if we can cleanly merge this to downstream 5.5.z, then there is no reason to wait.
This was fixed upstream in https://github.com/ManageIQ/manageiq/pull/5718
Verified in 5.6.0.4-beta2.3
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