Bug 1363897
| Summary: | Retirement state machine does not handle Ansible Tower services when part of a bundle | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Jerome Marc <jmarc> | ||||||
| Component: | Automate | Assignee: | William Fitzgerald <wfitzger> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Shveta <sshveta> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 5.6.0 | CC: | cpelland, dajohnso, jhardy, jmarc, kmorey, mkanoor, nstephan, obarenbo, simaishi, sshveta, tfitzger, wfitzger | ||||||
| Target Milestone: | GA | Keywords: | TestOnly, ZStream | ||||||
| Target Release: | 5.8.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | tower:service | ||||||||
| Fixed In Version: | 5.8.0.0 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1404746 1404747 (view as bug list) | Environment: | |||||||
| Last Closed: | 2017-06-12 16:44:05 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1404746, 1404747 | ||||||||
| Attachments: |
|
||||||||
Discussed issue with Kevin Morey who recommended a retirement instance for generic service types. New "Generic" instance should be used as the retirement entry point for Ansible Tower. Satoe, This PR has been merged so I am moving this to 'post'. Thanks Created a bundle with two service 1) Vmware catalog item and 2) Ansible Tower item . Ordered the bundle. Two separate services (one for vmware and one for ansible tower ) are provisioned under MyService. On retiring each service , the ansible tower job does not retire . Appliance : https://10.8.196.170 Service - bundle Shveta, I was using your appliance on Friday but its not working now. Is it still available? Thanks Billy https://10.8.198.83 Service bundle - "retire" The job under Automate - Ansible Tower - Job does not retire and keeps showing Hi Shveta, The Ansible Tower Service should not be shown in the UI when it is provisioned as part of a Service Bundle as reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1446452 Once the fix for the above BZ is merged, those sub services will not be shown. As long as the Ansible Tower job gets retired when the Bundle Service is retired, then it's not an issue. If you can validate the Bundle retirement works properly, we can validate this ticket. Let me know if you have any questions. Thanks, Tina Created attachment 1275965 [details] ansible job Hi Tina , What I am seeing is ansible service whether part of bundle or not does not retire the job . https://10.8.198.201 . I have created a catalog item here named ansible and retired it . The service moves to "retired" section in Myservice but the job (Under Automate-Ansible Tower- Jobs) does not retire . See attached screenshot . Isn't the job supposed to retire with service ? Hi Shveta, No, we don't do anything to the job. As long as the Service is marked as Retired, the retirement process has completed successfully. Thanks, Tina Verifying |
Created attachment 1187211 [details] Example of automation.log with loop on Ansible Tower service retirement Description of problem: I have a bundle setup with two services, first one is a VM provisioning, second is an Ansible Tower job template (specifying limit in the dialog). Provisioning is fine, but when retirering this service, the ServiceRetirement state machine goes in a loop at StartRetirement step (first step of the state machine) for the Ansible Type service. this causes CFME to become extremely slow and the automate.log to fill up with the same step being executed over and over (MIQ_ABORT is bot handle correctly). Example log attached. Version-Release number of selected component (if applicable): 5.6.0.13.20160624114606_13a9153 How reproducible: Always Steps to Reproduce: 1. Create a bundle with item 1) provision a VM, item 2) run Ansible Tower job template 2. Once the service provisioned, retire the service 3. CFME never completes the service retirement as seen in automation.log (loop for the ansible tower service retirement) Actual results: The retirement for the Ansible Tower service results with MIQ_ABORT but re-run the same retirement state machine over and over Expected results: Retirement state machine should stop, either successfully or with an error Additional info: Deleting the services manually (Services > My Services > Configuration > Remove Service from VMDB) causes the retirement service to complete.