Bug 1458011
| Summary: | Service Retirement not working properly for Orchestration Stacks due to missing zone. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Tina Fitzgerald <tfitzger> | ||||
| Component: | Control | Assignee: | Tina Fitzgerald <tfitzger> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Alex Newman <anewman> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 5.7.0 | CC: | akarol, cpelland, dajohnso, gekis, jhardy, jocarter, myoder, obarenbo, tfitzger, vaclav.miller | ||||
| Target Milestone: | GA | Keywords: | TestOnly, ZStream | ||||
| Target Release: | 5.9.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | stack:service:retirement:zone | ||||||
| Fixed In Version: | 5.9.0.1 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1461143 1465415 (view as bug list) | Environment: | |||||
| Last Closed: | 2018-03-06 14:41:19 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: | 1461143, 1465415 | ||||||
| Attachments: |
|
||||||
|
Description
Tina Fitzgerald
2017-06-01 18:46:54 UTC
Upon further investigation, the Service item to be retired should have put the work on the queue with the proper zone. The object type =>"ServiceOrchestration has a zone. We made a 5.7.3 change to log the zone when raising a retirement event. This change would be useful to the customer because they could see if the zone was specified, or defaulted: https://bugzilla.redhat.com/show_bug.cgi?id=1459307 Hi Gellart, fyi - The PR for this ticket covers the scenario where the orchestration stack is retired by itself, not as part of the service. Thanks, Tina New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/d8ef1675f1a8d7d6d401ae637921fab5a7d953ea commit d8ef1675f1a8d7d6d401ae637921fab5a7d953ea Author: Tina Fitzgerald <tfitzger> AuthorDate: Wed Jun 7 15:10:38 2017 -0400 Commit: Tina Fitzgerald <tfitzger> CommitDate: Thu Jun 8 10:05:10 2017 -0400 Add orchestration stack my_zone. https://bugzilla.redhat.com/show_bug.cgi?id=1458011 app/models/orchestration_stack.rb | 4 ++++ spec/models/service_orchestration_spec.rb | 11 +++++++++++ 2 files changed, 15 insertions(+) Created attachment 1287068 [details]
service debug rake task
Hi Gellert, No, the fix attached in this ticket covers the scenario where the customer is retiring the Orchestration Stack by itself and not through the Service. Attached is a debugging script the customer can run to log the details of a Service. Could you ask them to: 1. Copy the script to the /var/www/miq/vmdb/lib/tasks folder 2. From the vmdb folder run: bin/rake evm:service:inspect_service SERVICE_ID=123 where the service_id is from a Service that retirement failed on due to the zone. (Please ask them to do it for 2 - 3 Services.) 3. Capture and send us the script output. Let me know if you have any questions. Thanks, Tina New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/98922b099e1b105bd1c5214d3396e3b229e73d4b commit 98922b099e1b105bd1c5214d3396e3b229e73d4b Author: Tina Fitzgerald <tfitzger> AuthorDate: Thu Jul 6 16:06:20 2017 -0400 Commit: Tina Fitzgerald <tfitzger> CommitDate: Mon Jul 10 17:09:09 2017 -0400 Add my_zone to Service Orchestration. Zone is available through the Service VMs, but is incorrect when there are no Service VMs. https://bugzilla.redhat.com/show_bug.cgi?id=1458011 app/models/service_orchestration.rb | 4 ++++ spec/models/service_orchestration_spec.rb | 24 +++++++++++++++++++++--- 2 files changed, 25 insertions(+), 3 deletions(-) More recent information here: https://bugzilla.redhat.com/show_bug.cgi?id=1461143 I see that the customer case is closed. Do you need any additional information on this issue? |