Description of problem: With the resolution of https://bugzilla.redhat.com/show_bug.cgi?id=1142317 we should now add something to report back if the domain was readonly, and not just silently fail. Version-Release number of selected component (if applicable): 5.4.0.0.19 How reproducible: 100% Steps to Reproduce: 1. Create a automate method script 2. In the script call $evm.instance_create with the path containing the name of a readonly (locked) domain Actual results: The instance create will fail but no log generated Expected results: A log message should be generated, currently the log looks like this [----] I, [2015-04-16T06:57:21.777615 #24235:85f0c00] INFO -- : MiqAeService#instance_create << path="/ManageIQ/System/Request/Doughnut", values_hash={} Which looks like it passed, except it didn't :) Additional info:
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/1df41bf5ced73b30e23044f5c0484c6dfa6ac4dd commit 1df41bf5ced73b30e23044f5c0484c6dfa6ac4dd Author: Madhu Kanoor <mkanoor> AuthorDate: Thu Apr 16 09:59:03 2015 -0400 Commit: Madhu Kanoor <mkanoor> CommitDate: Thu Apr 16 09:59:03 2015 -0400 Log a warning for uneditable automate instances The automate methods $evm.instance_delete $evm.instance_update $evm.instance_create Have been returning a false for uneditable instances and the caller can check the return value and log an error. Based on the request from this ticket we will now log a warning if the instance is not editable https://bugzilla.redhat.com/show_bug.cgi?id=1212411 vmdb/lib/miq_automation_engine/engine/miq_ae_service.rb | 1 + 1 file changed, 1 insertion(+)
Verified in 5.4.0.1
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