New commit detected on ManageIQ/manageiq/fine:
Author: Greg McCullough <email@example.com>
AuthorDate: Thu Apr 19 08:47:41 2018 -0400
Commit: Greg McCullough <firstname.lastname@example.org>
CommitDate: Thu Apr 19 08:47:41 2018 -0400
Merge pull request #17280 from d-m-u/adding_lock_to_retire_now
Add lock to retire_now start
(cherry picked from commit 2deffa58399461396e3bbd57b93fc744f0c64e88)
app/models/mixins/retirement_mixin.rb | 43 +-
spec/models/service/retirement_management_spec.rb | 23 +-
spec/models/vm/retirement_management_spec.rb | 19 +
3 files changed, 67 insertions(+), 18 deletions(-)
VERIFIED in 18.104.22.168. I had 2 appliances in the same region connected to the same primary database. I was able to retire a VM and the retirement was started on a single machine and finished on another machine. There were no duplicate retirement events reported in the logs.
I recommend that the customer test this fix prior to closing the BZ due to the use of custom automate code in their environment
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.