Red Hat Bugzilla – Bug 1388493
Console should continue if error encountered gathering metrics
Last modified: 2017-07-24 10:11 EDT
Description of problem: The console periodically gathers metrics from the Hawkular Metrics endpoint. If an error is encountered, this will stop any further gathering of metrics. This means for the console to start displaying metrics again, the user has to reload their browser or change console tabs. It would be beneficial if the console could handle this situation in a better manner. We should be trying to gather metrics at the next interval in case the error has resolved itself, as well as potentially retrying once right after an error occurred.
https://github.com/openshift/origin-web-console/pull/930
Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/5c580bb8a7f85d952a35b39b9e8caca44c1c071d Bug 1388493 - Better handling of metrics errors If the first request for metrics fails, show an empty state error message. Otherwise show an alert if more than one consecutive request fails. The alert has a retry link. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1388493
Will check when new puddle is ready
Which OCP puddle contains the fix for the bug? And to verify the bug, what kind of error should I simulate so that I can see the alert info?
Sorry, I thought the bug was opened against origin. Changing status to MODIFIED.
This has been merged into ocp and is in OCP v3.5.0.7 or newer.
Checked on OCP v3.5.0.7 Check pod's metrics on web console, metrics chart is updated periodically when metrics endpoint is working. When the metrics endpoint doesn't work, the pod metrics chart won't update and when gather metrics at the next interval, there is an alert info showing with a "Retry" link, user could click it to retry, once the metrics endpoint is ok, the error will disappear: "An error occurred updating metrics for pod nodejs-1-d7php. Retry" The bug has been fixed, so move it to verified.
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-2017:0884