Hide Forgot
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/7051ce276be724232cd2d0b4e46b31e8e24f2ab1 commit 7051ce276be724232cd2d0b4e46b31e8e24f2ab1 Author: Greg McCullough <gmccullo@redhat.com> AuthorDate: Wed May 10 10:23:00 2017 -0400 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Wed May 10 11:25:54 2017 -0400 Merge pull request #18 from tinaafitz/add_zone_to_qoptions Add zone to q_options in call_automate. (cherry picked from commit 0495c11579d5751f91c6e6791c65cdd1db09ad88) https://bugzilla.redhat.com/show_bug.cgi?id=1449753 lib/miq_automation_engine/engine/miq_ae_event.rb | 1 + .../lib/miq_automation_engine/miq_ae_event_spec.rb | 55 +++++++++++++++++++--- 2 files changed, 49 insertions(+), 7 deletions(-)
New commit detected on ManageIQ/manageiq/euwe: https://github.com/ManageIQ/manageiq/commit/2bac4be51677a1bd931ffc2a2f5d871dbf6d2cce commit 2bac4be51677a1bd931ffc2a2f5d871dbf6d2cce Author: Greg McCullough <gmccullo@redhat.com> AuthorDate: Wed May 10 10:42:12 2017 -0400 Commit: Satoe Imaishi <simaishi@redhat.com> CommitDate: Wed May 10 11:27:49 2017 -0400 Merge pull request #15026 from tinaafitz/add_zone_to_retirement Change retire_now to pass zone_name to raise_retirement_event. (cherry picked from commit 9e5df30604b9c0fb9fdbb91952a4d70f3fe7abf4) https://bugzilla.redhat.com/show_bug.cgi?id=1449753 app/models/mixins/retirement_mixin.rb | 10 +++++++++- .../models/orchestration_stack/retirement_management_spec.rb | 7 ++++--- spec/models/service/retirement_management_spec.rb | 6 +++--- spec/models/vm/retirement_management_spec.rb | 12 ++++++++---- 4 files changed, 24 insertions(+), 11 deletions(-)
The issue is that the orchestration stack does not have a zone. The code change included in this ticket uses the zone, if available, when putting retirement events on the queue. A separate ticket has been opened to address this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1458011
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/RHSA-2017:1601