Bug 1207788
Summary: | "VM Power off" event is called instead of "VM Power Off Request" when powering off an vm from CFME | ||
---|---|---|---|
Product: | Red Hat CloudForms Management Engine | Reporter: | Ramesh A <rananda> |
Component: | Control | Assignee: | Bill Wei <bilwei> |
Status: | CLOSED ERRATA | QA Contact: | Ievgen Zapolskyi <izapolsk> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.4.0 | CC: | dajohnso, jhardy, mfalesni, mfeifer, obarenbo |
Target Milestone: | GA | Flags: | izapolsk:
automate_bug-
|
Target Release: | 5.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-06-16 12:56:24 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ramesh A
2015-03-31 17:17:48 UTC
Bill - I do not see where in the code vm_poweroff ever gets passed to enforce_policy directly. Would be useful to recreate and inject a stack dump into the enforce_policy method. New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/1614100e26393ba53e59a2a0613257feb6d92645 commit 1614100e26393ba53e59a2a0613257feb6d92645 Author: Bill Wei <bilwei> AuthorDate: Mon Apr 6 17:18:28 2015 -0400 Commit: Bill Wei <bilwei> CommitDate: Mon Apr 6 17:18:28 2015 -0400 Correct event name from request_vm_stop to request_vm_poweroff request_vm_stop is not a valid event name https://bugzilla.redhat.com/show_bug.cgi?id=1207788 vmdb/app/models/vm_or_template/operations/power.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Good to go. Verified and working fine in 5.4.0.0.22.20150420163946_26004d1. 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://rhn.redhat.com/errata/RHBA-2015-1100.html |