Description of problem: Service retirement of Orchestration Stacks not queueing retirement to the proper zone. Service retirement will attempt to queue retirement for the service item in the proper zone if it's available. Orchestration stacks currently don't have the zone defined, so no zone is used during retirement queueing. More information: https://bugzilla.redhat.com/show_bug.cgi?id=1447625
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.
https://github.com/ManageIQ/manageiq/pull/15334
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?