Bug 1652956

Summary: retirement of the parent service does not retire ansible tower and aws orchestration child items
Product: Red Hat CloudForms Management Engine Reporter: Felix Dewaleyne <fdewaley>
Component: AutomateAssignee: Tina Fitzgerald <tfitzger>
Status: CLOSED CURRENTRELEASE QA Contact: Nandini Chandra <nachandr>
Severity: high Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: high    
Version: 5.9.5CC: dmetzger, fdewaley, mkanoor, obarenbo, simaishi, tfitzger, vaclav.miller
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.10.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 5.10.0.28 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1656169 1660602 (view as bug list) Environment:
Last Closed: 2019-02-12 16:50:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1656169, 1660602    

Description Felix Dewaleyne 2018-11-23 16:53:22 UTC 
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
Comment 5 Tina Fitzgerald 2018-11-28 18:54:35 UTC 
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
Comment 6 Tina Fitzgerald 2018-11-29 20:58:17 UTC 
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
Comment 7 Tina Fitzgerald 2018-12-04 16:19:41 UTC 
Moving to POST since the following PRs resolve this issue:

https://github.com/ManageIQ/manageiq/pull/18251
https://github.com/ManageIQ/manageiq/pull/18252
Comment 9 Tina Fitzgerald 2018-12-17 20:22:58 UTC 
Adding 5.8.z flag per conversation with Dennis.
Comment 11 Nandini Chandra 2019-02-01 18:16:55 UTC 
This issue is not specific to Ansible . The issue is that retiring a service bundle doesn't retire child catalog items.
Comment 12 Nandini Chandra 2019-02-01 19:15:38 UTC 
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