Created attachment 1016603 [details] Flash message in red Description of problem: ---------------------- This report generation status message is displayed in red even when there are no errors(see attached screen shot). Report generation returned: Status [Ok] Message [Task has been queued] Version-Release number of selected component (if applicable): ---------------------- 5.4.0.0.19.20150410165622_ad23806 How reproducible: ---------------- Always Steps to Reproduce: --------------------- 1.Attempt to download the same report a number of times. Actual results: -------------- The report generation status message is displayed in red even when there are no errors. Expected results: ---------------- The report generation status message should be displayed in green if there are no errors. Additional info: ---------------
https://github.com/ManageIQ/manageiq/pull/6613
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/afebe142dab45fa58e4ea01d8cacabe7a5eb2959 commit afebe142dab45fa58e4ea01d8cacabe7a5eb2959 Author: Brian McLaughlin <bmclaugh> AuthorDate: Thu Feb 11 10:48:17 2016 -0500 Commit: Brian McLaughlin <bmclaugh> CommitDate: Thu Feb 11 16:30:51 2016 -0500 Fix incorrect flash message when downloading a Report Code change keeps the spinner active until the download begins, preventing the user from repeatedly downloading numerous copies of a Report. https://bugzilla.redhat.com/show_bug.cgi?id=1213617 app/assets/javascripts/miq_application.js | 31 ++++++++++++++++--------------- spec/javascripts/miq_application_spec.js | 23 +++++++++++++++++++++++ 2 files changed, 39 insertions(+), 15 deletions(-)
https://github.com/ManageIQ/manageiq/pull/6577
Detected commit referencing this ticket while ticket status is MODIFIED.
Unrelated PR that was closed immediately.
Verified in 5.6 Beta 2.
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-2016:1348