New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/f5a156b6583ca757b84e372455df7b1c5b95e368 commit f5a156b6583ca757b84e372455df7b1c5b95e368 Author: Brandon Dunne <bdunne> AuthorDate: Tue Aug 20 16:36:52 2019 -0400 Commit: Brandon Dunne <bdunne> CommitDate: Tue Aug 20 16:36:52 2019 -0400 Merge pull request #19143 from lfu/dup_service_retire_request_18558 Service retirement request should be per region. (cherry picked from commit 3ab4626c51447481724d8b720c9e83c0ee788a9d) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1764197 app/models/miq_schedule_worker/jobs.rb | 1 + app/models/retirement_manager.rb | 7 +- spec/models/retirement_manager_spec.rb | 13 +- 3 files changed, 16 insertions(+), 5 deletions(-)
Hi Tina, Please provide steps and expected result to verify this BZ? This will be very helpful :) Thanks, Ganesh
Hi Ganesh, 1. Setup an environment where you have 2 appliances in the same region, each with their own zone. 2. Create a service item that provisions a VM(the type doesn't matter) 3. Order the service to ensure it provisions the VM properly. 4. Navigate to the Active Services page, and select lifecycle, set retirement date, to today. 5. Look for RetirementManager.check in the appliances evm.log, and look for retirement being called twice for the same service. Note - I can help with step 5, just ping me with the service name and appliance ip addresses. Let me know if you have any questions. Thanks, Tina
Thank you so much @Tina for detailed steps. I have created setup with two appliance in one region and added them into different zones. And performed other steps. I can see RetirementManager.check ran on both appliances but the request to retire the service only happened once. Hence verifying this BZ on version: 5.10.12.1.20191022171907_f883bde
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. https://access.redhat.com/errata/RHBA-2019:3268
updating test coverage flag based on the original BZ - BZ1748353