Red Hat Bugzilla – Bug 1461143
Service Retirement not working properly for Orchestration Stacks due to missing zone.
Last modified: 2017-08-14 12:11:46 EDT
New commit detected on ManageIQ/manageiq/fine:
Author: Greg McCullough <firstname.lastname@example.org>
AuthorDate: Thu Jun 8 10:43:30 2017 -0400
Commit: Satoe Imaishi <email@example.com>
CommitDate: Tue Jun 13 12:05:17 2017 -0400
Merge pull request #15334 from tinaafitz/orchestration_stack_add_zone
Add orchestration stack my_zone.
(cherry picked from commit 8e6d2fb05a36be637183b083efafbe7904f58e8d)
app/models/orchestration_stack.rb | 4 ++++
spec/models/service_orchestration_spec.rb | 11 +++++++++++
2 files changed, 15 insertions(+)
Thanks for the log.
Can you ask the customer to send screen shots of the following Service Catalog Items, showing the basic information including provider.
OpenStack basic VM - Windows type: <ServiceTemplateOrchestration
OpenStack VM with SLM - Linux type: <ServiceTemplateOrchestration
I suspect those Service catalog items are missing the provider.
We're working on new test cases for this issue and one important scenario we didn't discuss here is if the Services in question here have VMs or not.
Would you ask the customer if the Services that are not retiring properly have associated VMs?
Retirement appears to be working for me. Hesitant to move this to verified without hearing from customer. I'm going to leave it ONQA for a bit.
Did you do retire an Orchestration Service wit,h and without a VM? I think the no VM retirement could be the issue here.
Hi Tina ,
I have an appliance with a zone .
Added the provider to the zone.
Provisioned one orchestration service with VM and one without VM.
Retired both service from "My Service"
Both services were retired .
Is this good to verify the fix?
Provision a service with VM in default zone.
Once the service is provisioned .Switch the provider to new zone.
retire service .
log message shows request_service_retire queue put in the correct zone "newzone".
Retired a service without VM and service got retired in default zone.
Verified in 126.96.36.199.20170725160636_e433fc0
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
I see that the customer case is closed.
Do you need any additional information on this issue?