Description of problem: When trying to retire a service bundle, the service won't retire and the VMs under it are orphaned instead of retired or archived Version-Release number of selected component (if applicable): 5.9.6 How reproducible: Always Steps to Reproduce: 1. Create a service bundle 2. Order service bundle 3. Retire service bundle Actual results: The service is not retired, VMs are oprhaned, VMs are removed from within the provider Expected results: Service retires and the VMs are archived Additional info:
Tested Service Bundle retirement on 5.9.6.5.20181130162459_7977a85. Recreated issue where sub services were not retired, causing retirement to retry until max_retires, then error out. The VM's were properly retired. Applied fix(reverted retirement change) and retested. Service and all of its sub services(and VMs) were properly retired.
https://github.com/ManageIQ/manageiq/pull/18252 was reverted commit dd72793edf2f7301a9db8559250f19eec35f99dc Author: Satoe Imaishi <simaishi> Date: Tue Dec 18 11:06:15 2018 -0500 Revert "Merge pull request #18252 from d-m-u/fixing_bundled_service_retirement" This reverts commit 7977a85146ec6a38105858d3eac566eea5bf7c23, reversing changes made to dd593c38442ce6d6d6fd6e1338156a8ee663b7d8.
Created attachment 1516163 [details] hotfix-cfme-5.9.6.5-4
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-2019:0110