Description of problem: retirement of the parent service does not retire ansible tower and aws orchestration child items Version-Release number of selected component (if applicable): 5.9.5.3-2 How reproducible: all the time Steps to Reproduce: 1. create a bundle that provisions an ansible tower item and an aws orchestration 2. provision the service 3. retire the bundle Actual results: the top service is retired but the items are not Expected results: the items are retired Additional info: the logs show no trace of the service items being retired (the 2 child services don't get retired at all) this seems close to bz#1608958
Hi Felix, We have another ticket that we think has the same root cause, and would benefit with the same fix. We're working with the customer to test the fix, and would make an official fix once the customer verifies the change. I'll send an update once I have more information. Regards, Tina
Hi Felix, As discussed in several cf-prio email threads, we have identified the root cause of the retirement issue to be a Service linking issue for which we are currently test a fix. I'll send an update once we have more information. Thanks, Tina
Moving to POST since the following PRs resolve this issue: https://github.com/ManageIQ/manageiq/pull/18251 https://github.com/ManageIQ/manageiq/pull/18252
Adding 5.8.z flag per conversation with Dennis.
This issue is not specific to Ansible . The issue is that retiring a service bundle doesn't retire child catalog items.
Marking this as VERIFIED since the VMs created through child catalogs get retired. vmdb_production=# select id, name, retirement_state, ancestry from services order by id; id | name | retirement_state | ancestry ----+--------------------------------+------------------+---------- 7 | cat-bundle | retired | 8 | cat-item2 | retired | 7 9 | service-cback | retired | 7 Verified in 5.10.0.32