Description of problem: The miq_request.user_message method sets the "Last Message" only for state machine error conditions and/or the finished state. Long running state machines would not report correct "Last Message" until the end of the state machine. Changing the user_message= method to set the miq_request.message will report an accurate "Last Message" status. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/4907d31d6e3bfeebbaa427754abde15edb9d3384 commit 4907d31d6e3bfeebbaa427754abde15edb9d3384 Author: Tina Fitzgerald <tfitzger> AuthorDate: Thu Apr 2 14:45:23 2015 -0400 Commit: Tina Fitzgerald <tfitzger> CommitDate: Tue Apr 7 18:49:37 2015 -0400 Updated miq_request.user_message to set miq_request.message attribute. https://bugzilla.redhat.com/show_bug.cgi?id=1196369 vmdb/app/models/mixins/miq_request_mixin.rb | 1 + ...iq_ae_service_service_template_provision_request_spec.rb | 13 +++++++++++-- .../miq_ae_service_service_template_provision_task_spec.rb | 11 +++++++++++ 3 files changed, 23 insertions(+), 2 deletions(-)
PR was merged. https://github.com/ManageIQ/manageiq/pull/2507
https://github.com/ManageIQ/manageiq/pull/2507 Validation steps here: https://bugzilla.redhat.com/show_bug.cgi?id=1161253 The difference is that you should see the "Last Message" for miq_request immediately when setting the user message, rather than when the service is complete. The previous change for the miq_request.user_message method set the "Last Message" only for state machine error conditions and/or the finished state, long running state machines would not report correct "Last Message" until the end of the state machine. Changed the user_message= method to set the miq_request.message to report an accurate "Last Message" status during state machine processing.
Last message set immediately Verified in 5.4.0.0.26.20150511144816_f924bd4
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