Bug 1783361
| Summary: | Unable to use the "prevent current event from proceeding" action on a "VM Retire Request" event | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | Satoe Imaishi <simaishi> |
| Component: | Control | Assignee: | Lucy Fu <lufu> |
| Status: | CLOSED ERRATA | QA Contact: | John Dupuy <jdupuy> |
| Severity: | medium | Docs Contact: | Red Hat CloudForms Documentation <cloudforms-docs> |
| Priority: | medium | ||
| Version: | 5.10.3 | CC: | bmidwood, dmetzger, jdupuy, lufu, obarenbo, tfitzger, wfitzger |
| Target Milestone: | GA | Keywords: | Regression, ZStream |
| Target Release: | 5.10.14 | Flags: | simaishi:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 5.10.14.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1702018 | Environment: | |
| Last Closed: | 2020-01-21 16:51:47 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | CFME Core | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1702018 | ||
| Bug Blocks: | |||
|
Comment 3
CFME Bot
2019-12-13 16:21:05 UTC
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 |