Bug 1468635
| Summary: | unable to retire a bundle containing ansible tower service in 5.8 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Felix Dewaleyne <fdewaley> | ||||
| Component: | Providers | Assignee: | Bill Wei <bilwei> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nandini Chandra <nachandr> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.8.0 | CC: | ahoness, bilwei, cpelland, dajohnso, dberger, dluong, duhlmann, fdewaley, gblomqui, gekis, gmccullo, jfrey, jhardy, jwarnica, kkulkarn, nachandr, obarenbo, simaishi, tfitzger, vdulava | ||||
| Target Milestone: | GA | Keywords: | Reopened, TestOnly, ZStream | ||||
| Target Release: | 5.10.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | provider:azure:storage | ||||||
| Fixed In Version: | 5.10.0.0 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1600670 (view as bug list) | Environment: | |||||
| Last Closed: | 2019-02-11 13:55:40 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | Azure | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1600670 | ||||||
| Attachments: |
|
||||||
|
Description
Felix Dewaleyne
2017-07-07 15:18:36 UTC
Drew, I suggest we add a noop raw_delete_stack method for the Ansible Tower subclass of OrchestrationStack. Hi Felix, We're still looking into the issue, but we haven't been able to reproduce it. I've attached a rake script for the customer to run on the Services in question. The script logs all of the Service information. Could you ask the customer the following: 1. Copy the attached evm_service.rake file to vmdb/lib/tasks folder. 2. Run the inspect_service rake command for 2 of the Orchestration Services that exhibit the reported behavior. 3. Send us the rake task output. Two ways to inspect a service, by service or request id: bin/rake evm:service:inspect_service SERVICE_ID=13 bin/rake evm:service:inspect_service REQUEST_ID=208 Thanks, Tina Created attachment 1307201 [details]
service rake script
the issue is still present and the customer has re-started communicating with us - they provided new logs. Hi Felix, Based on the case history here with the refresh issues, I'm not confident of the state of the provisioned Services as it relates to retirement. I'd like the customer to start by provisioning a Service, then immediately retire the Service, sending us the logs which include the full provisioning and retirement processes along with the Service ID/name and Request ID. Thanks, Tina (In reply to Tina Fitzgerald from comment #17) > Hi Felix, > > Based on the case history here with the refresh issues, I'm not confident of > the state of the provisioned Services as it relates to retirement. > > I'd like the customer to start by provisioning a Service, then immediately > retire the Service, sending us the logs which include the full provisioning > and retirement processes along with the Service ID/name and Request ID. > > Thanks, > Tina the customer said they would provide the data today, I'll share it as soon as it is available. Hey Felix! Is there any update on this issue? (In reply to drew uhlmann from comment #19) > Hey Felix! Is there any update on this issue? I have the data! let me see how I can share it... Hey Felix! I'm so sorry about this, but the timestamps on the evm log do not make much sense to me. The event of interest starts at 20:19 on 9/27 but the evm log times only cover 3:11 to 5:23 and thus don't include the pertinent information about the event. Could you please send us a copy of the relevant logs? (In reply to drew uhlmann from comment #22) > Hey Felix! I'm so sorry about this, but the timestamps on the evm log do not > make much sense to me. The event of interest starts at 20:19 on 9/27 but the > evm log times only cover 3:11 to 5:23 and thus don't include the pertinent > information about the event. Could you please send us a copy of the relevant > logs? the logs I shared on the private server are all I have. I can request to get new data, the complete set of logs from the customer is available in the parent folder *** Bug 1497175 has been marked as a duplicate of this bug. *** please let me know if I absolutely need to request new data based on the inconsistency. In customer's setup they created a bundle which included three Ansible Tower services and one Azure Orchestration Stack service. When the bundle was retried, automate attempted to retire all services. Two problems have been reported from the retirement operation: 1. Error: method raw_stack_delete not implemented. It came from retiring Ansible Tower services. Ansible Tower Job, although a subclass of OrchestratioStack does not support retirement. We can fix the issue by skipping Ansible Tower Job retirement. 2. Disk not removed. The reason should be found in azure.log. I have posted the analysis in BZ 149715. Sorry, The above BZ should be BZ 1497175 Hi Greg, Yes, we would have to change the retirement code for the Ansible Tower job. I'm going to assign it to Bill. Thanks, Tina New commit detected on ManageIQ/manageiq-providers-ansible_tower/master: https://github.com/ManageIQ/manageiq-providers-ansible_tower/commit/91048c5b4f7f2a6abc0e0509e06b3508215c52e3 commit 91048c5b4f7f2a6abc0e0509e06b3508215c52e3 Author: Bill Wei <bilwei> AuthorDate: Tue Mar 6 10:49:46 2018 -0500 Commit: Bill Wei <bilwei> CommitDate: Tue Mar 6 10:49:46 2018 -0500 Move #retire_now to shared code https://bugzilla.redhat.com/show_bug.cgi?id=1468635 app/models/manageiq/providers/ansible_tower/shared/automation_manager/job.rb | 4 + spec/support/ansible_shared/automation_manager/job.rb | 7 + 2 files changed, 11 insertions(+) New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/6f62e35a59e806fa5948ab28e7bc01f4605a8cc2 commit 6f62e35a59e806fa5948ab28e7bc01f4605a8cc2 Author: Bill Wei <bilwei> AuthorDate: Tue Mar 6 10:53:31 2018 -0500 Commit: Bill Wei <bilwei> CommitDate: Tue Mar 6 10:53:31 2018 -0500 Delete #retire_now since it has been moved to shared code fixes https://bugzilla.redhat.com/show_bug.cgi?id=1468635 app/models/manageiq/providers/embedded_ansible/automation_manager/job.rb | 5 - spec/models/manageiq/providers/embedded_ansible/automation_manager/job_spec.rb | 5 - 2 files changed, 10 deletions(-) No requestee for needinfo set, can you take a look and determine where this should go? No requestee for needinfo set, can you take a look and determine where this should go? *** Bug 1565418 has been marked as a duplicate of this bug. *** Verified in 5.10.0.22 |