Service Retirement has been calling service retirement 2 times for each sub-service. Although the double retirement calls aren't necessary, they shouldn't cause any issues. Any item(s) are skipped over once they're retired. Steps to Reproduce: 1. Provision A Service Bundle containing a Single Child Service. 1. Retire the Service Bundle. 2. Search logs for Service.retire_now. (Look for the sub service name for the Service.retire_now since there will be a Service.retire_now call for the Bundled Service) Actual results: Double call for the sub-service Service.retire_now call. Expected results: Should only be a single call for the sub-service Service.retire_now. Additional info: The PR was initially posted to this ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1600670
https://github.com/ManageIQ/manageiq/pull/17881
Per https://github.com/ManageIQ/manageiq/pull/17881#issuecomment-416719204, the PR linked that fixes this issue can't be merged yet.
Verified on 5.9.5.1.
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/RHSA-2018:3466