Description of problem: Clicking on refresh icon to refresh log file content doesn't show any in-progress icon. If the file is huge and has got many new files, its "reload" takes time and the user doesn't know if anything is happening in the background. There should be an overlay over currently loaded log file content with in-progress wheel icon to inform the user "we" are doing something. Version-Release number of selected component (if applicable): redhat-support-plugin-rhev-3.4.0-4.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. select vdsm.log or some other huge file into Log Viewer 2. click refresh icon to update diplayed log file content 3. Actual results: no idea if it works or not if the file is huge as there's no in-progress wheel icon Expected results: let's clearly inform the user there's ongoing work in the background so he knows why is he waiting Additional info:
https://github.com/redhataccess/redhat_access_angular_ui/commit/3b2fc94fc2489d0d849ca2e02711c8245f57c0a9
out of scope for 3.4.2, missing from tracker bug: [RHEV] 3.4.2 Bug tracker - https://bugzilla.redhat.com/show_bug.cgi?id=1123858. moving to 3.4.3
fail, i don't see any in-progress icon/circle, just the log get appended. redhat-support-plugin-rhev-3.5.0-0.el6ev.noarch
ok, redhat-support-plugin-rhev-3.5.0-1.el6ev.noarch
Cause: When the user clicked the refresh icon a in-progress icon was not show. Consequence: The user would not know if a file refresh action was happening. Fix: Display an in-progress icon when a file refresh is happening. Result: The user now knows when a file refresh is happening.
Spenser, please mark the require_doc_text flag as '-' if any of these bugs needs doc for errata or ? if you need to document it and request assistance from doc team? this is needed asap for the last rc build due this week.
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-0211.html