Hi Yoder, We've been looking at the Services on the reproducer appliance, and we know why retirement is not retiring the sub service. The top level service(Service bundle) has a service_resource for the sub service. The sub service, service_resource is supposed to have a resource for the service, and it doesn't on this specific version. We're in the process of figuring out why the service_resource,resource doesn't exist. I'll have an update later today. Thanks, Tina
Hi Yoder, As we discussed, can you ask the customer if they would be willing to try a one line code change? They would have to restart the appliance and turn off the Automate role on the other appliances. The code change is here: https://github.com/ManageIQ/manageiq/pull/17881/files#diff-610ed908579256e82c76ec0910169142 To test the code change: 1. Navigate to the vmdb/app/models/service folder. 2. Copy the retirement_management.rb to retirement_management.rb.original (cp -p retirement_management.rb retirement_management.rb.orig) 3. Edit retirement_management.rb, adding this line: direct_service_children.each(&:retire_service_resources) immediately after this line: def retire_service_resources 4. restart the appliance 5. Retire Service Bundle Let me know if you have any questions. Thanks, Tina
Hi Gellert, 1. Can you ask the customer for the entry point of the Service Bundle and of each service item? I see this in the new automation.log retirement_entrypoint: /Cloud/Orchestration/Retirement/StateMachines/StackRetirement/Default This should be a service entry point. The customer stated: "But on the other hand, I've created a catalog bundle that contains only the azure orchestration catalog item (this is temporally, the intention is to also add ansible towers items). It creates the service correctly, but the problem is when I try to retire it, the service is successfully retired, but resources created with the azure orchestration aren't deleted." 2. Did the customer try to retire the Service Bundle as described above? If not, can you ask them to retire it? (With a single item) 3. Does the Service show as retired? 4. It looks like custom code is in use in retirement. Can the customer disable the custom domains before retiring the service? Let me know if you have any questions. Thanks, Tina
https://github.com/ManageIQ/manageiq/pull/18244
Hi Gellert, I'm glad to hear the customer was able to successfully retire the Service. Although the problem shows up in retirement, the root cause is a provision issue which we've identified and for which we are currently testing a fix. I'll send an update once we have more information. Thanks, Tina
https://github.com/ManageIQ/manageiq/pull/18251
Although this reported as a retirement issue, the root cause is a service linking issue which is resolved with the PR referenced in comment 15.
New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/b14870058edc22e3e60f26064a928c11cb5a9240 commit b14870058edc22e3e60f26064a928c11cb5a9240 Author: Greg McCullough <gmccullo> AuthorDate: Thu Nov 29 18:48:45 2018 -0500 Commit: Greg McCullough <gmccullo> CommitDate: Thu Nov 29 18:48:45 2018 -0500 Merge pull request #18251 from d-m-u/fixing_service_bundle_resource_linking Link service resources of bundled service correctly (cherry picked from commit 4cdafdbf809ecf69b80b210abfcd5c7f28629259) https://bugzilla.redhat.com/show_bug.cgi?id=1653648 app/models/service_template.rb | 4 +- spec/models/service_template_spec.rb | 42 +- 2 files changed, 35 insertions(+), 11 deletions(-)
clearing needinfo
Adding 5.8.z flag per conversation with Dennis.
Hi Nandini, Can you retire a Service bundle containing only service items, not bundles? Thanks, Tina
Hi Nandini, Can you provide the reproducer IP address? Thanks, Tina
Hi Nandini, This is a blocker bug, and the build is next week. Can you provide a reproducer environment? Thanks, Tina
We expect this is fixed in the as-yet-unmerged https://github.com/ManageIQ/manageiq/pull/18283
Hi Niyaz, We're still testing our changes on the 10.8.198.150 reproducer environment. Can we continue to use this appliance for at least the next week, or until we have the new 5.10 build? Thanks, Tina
Hi Tina, sure you can use this appliance.
Catalog bundle resources now retiring Verified in Version 5.10.0.31.20190108221820_a0968c8