Description of problem: Retirements do not currently have Service IDs like Lifecycle and Service Provisioning. Giving retirements a unique ID will make it easier to track retirements in the logs and/or in the Web UI. Version-Release number of selected component (if applicable): all How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This request is for the CloudForms Support Team to help troubleshoot retirement issues.
Enhancement done in PR https://github.com/ManageIQ/manageiq/pull/17013
Appliance version: 5.10.0.3 "service_template_provision_request" and "service_template_provision_task" and also "miq_provision" are now prefixed with the letter 'r' plus 'request_id'. However, there is bz 1599299 and I can't verify how it looks upon service retirement, which is what this BZ talks about. Going to mark this as FAILED_QA until the upper mentioned BZ is resolved, then will retest.
Hi Antonin, The above referenced BZ has been verified. Can you retest? Thanks, Tina
appliance version: 5.10.0.8. "vm_retire_task" and "service_retire_task" are also prefixed. This works fine.
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-2019:0212