New commit detected on ManageIQ/manageiq-content/hammer: https://github.com/ManageIQ/manageiq-content/commit/8945d950176efb5086ce4537e512a3f04fb90366 commit 8945d950176efb5086ce4537e512a3f04fb90366 Author: Madhu Kanoor <mkanoor> AuthorDate: Wed Aug 14 17:52:01 2019 -0400 Commit: Madhu Kanoor <mkanoor> CommitDate: Wed Aug 14 17:52:01 2019 -0400 Merge pull request #552 from lfu/prevent_retirement_1702018 Vm retirement is processed by VmRetireRequest state machine. (cherry picked from commit 3e2fb4beb1c6d214ca62daa65eb9856d6cc69a5c) https://bugzilla.redhat.com/show_bug.cgi?id=1783361 content/automate/ManageIQ/System/Event/MiqEvent/POLICY.class/request_vm_retire.yaml | 6 - 1 file changed, 6 deletions(-)
https://github.com/ManageIQ/manageiq/pull/19643
New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/16543b7ac8a5db590f053e4c6d8e326e8e315450 commit 16543b7ac8a5db590f053e4c6d8e326e8e315450 Author: Lucy Fu <lufu> AuthorDate: Tue Aug 13 10:07:38 2019 -0400 Commit: Lucy Fu <lufu> CommitDate: Tue Aug 13 10:07:38 2019 -0400 Add policy check to Vm retirement. https://bugzilla.redhat.com/show_bug.cgi?id=1783361 app/models/vm_or_template.rb | 19 + spec/models/vm/retirement_management_spec.rb | 45 +- 2 files changed, 57 insertions(+), 7 deletions(-)
Verified in CFME 5.10.14.0.20200107223945_aa73a61 Steps of verification: 1. Add infra provider (I noticed this with VMWare 6.5) 2. Provision a vm on that provider 3. Create a Vm Control policy with settings detailed in the attached image 4. Assign the policy to a profile 5. Assign the profile to the infra provider 6. Retire the VM via the UI 7. Wait 5-10 min Verified that the VM was NOT retired after 5-10 min. Therefore the policy and action to prevent the retirement request worked properly.
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-2020:0189