Backported to Hammer branch: commit b8ec07a2fac279d9e3f5e40c3061df85e7055188 Author: Greg McCullough <gmccullo> Date: Tue Jan 15 16:15:32 2019 -0500 Merge pull request #287 from d-m-u/fixing_message_thing Don't overwrite message in create_automation_object (cherry picked from commit f38c83c12af9154651f3f18f6febf2a762003cd9) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1672693
New commit detected on ManageIQ/manageiq-automation_engine/hammer: https://github.com/ManageIQ/manageiq-automation_engine/commit/b8ec07a2fac279d9e3f5e40c3061df85e7055188 commit b8ec07a2fac279d9e3f5e40c3061df85e7055188 Author: Greg McCullough <gmccullo> AuthorDate: Tue Jan 15 16:15:32 2019 -0500 Commit: Greg McCullough <gmccullo> CommitDate: Tue Jan 15 16:15:32 2019 -0500 Merge pull request #287 from d-m-u/fixing_message_thing Don't overwrite message in create_automation_object (cherry picked from commit f38c83c12af9154651f3f18f6febf2a762003cd9) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1672693 lib/miq_automation_engine/engine/miq_ae_engine.rb | 1 - spec/miq_ae_engine_spec.rb | 9 + 2 files changed, 9 insertions(+), 1 deletion(-)
Created attachment 1535878 [details] verification It works fine as per BZ steps.
Hi Nikhil, It looks there's a difference in what was specified between simulate and the custom button execution: The button execution has YTALE as the message; [----] I, [2019-02-18T04:52:14.989631 #9814:51cf5c] INFO -- : Followed Relationship [miqaedb:/System/custom_request/instance_1#YTALE] [----] I, [2019-02-18T04:52:14.990176 #9814:51cf5c] INFO -- : Followed Relationship [miqaedb:/System/Request/Call_Instance_With_Message#create] Simulate does not have the message specified(or has create as the message) [----] I, [2019-02-18T04:51:47.631004 #10135:fc295c] INFO -- : Followed Relationship [miqaedb:/System/custom_request/instance_1#create] [----] I, [2019-02-18T04:51:47.631902 #10135:fc295c] INFO -- : Followed Relationship [miqaedb:/System/Request/Call_Instance_With_Message#create] Using the attribute section of simulate, you can specify the key: message with value: YTALE which should make a difference in the log output. Let me know if you have any questions. Thanks, Tina
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-2019:0453