Description of problem: These charts in k8s-resources-namespace dashboard are not shown in console: Receive Bandwidth Transmit Bandwidth Rate of Received Packets Rate of Transmitted Packets Rate of Received Packets Dropped Rate of Transmitted Packets Dropped and there's "pod is not defined error" This error is also found in 'k8s-resources-pod' dashboard Version-Release number of selected component (if applicable): 4.4.0-0.nightly-2020-02-07-001901 How reproducible: Always Steps to Reproduce: 1. visit /monitoring/dashboards page, choose k8s-resources-namespace from drop down list Actual results: 1. There are errors in browser console, also some charts are not shown either while these charts are correctly shown in Grafana console Receive Bandwidth Transmit Bandwidth Rate of Received Packets Rate of Transmitted Packets Rate of Received Packets Dropped Rate of Transmitted Packets Dropped ReferenceError: "pod is not defined" anonymous vendors~main-chunk-93d333ee75638f5125d7.min.js line 12 > Function:8 p 208-chunk-3bf09a7292229ace4248.min.js:1 j 208-chunk-3bf09a7292229ace4248.min.js:1 a vendors~main-chunk-93d333ee75638f5125d7.min.js:4755 a vendors~main-chunk-93d333ee75638f5125d7.min.js:4755 j 208-chunk-3bf09a7292229ace4248.min.js:1 a vendors~main-chunk-93d333ee75638f5125d7.min.js:4755 a vendors~main-chunk-93d333ee75638f5125d7.min.js:4755 a vendors~main-chunk-93d333ee75638f5125d7.min.js:4755 ue 208-chunk-3bf09a7292229ace4248.min.js:1 Li vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 ha vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 da vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 fa vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Ku vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Bu vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Nu vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Iu vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 ho vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 unstable_runWithPriority vendors~main-chunk-93d333ee75638f5125d7.min.js:149587 so vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 ho vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 po vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Au vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 $i vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 pe 208-chunk-3bf09a7292229ace4248.min.js:1 backend.js:6:2315 r backend.js:6 Ia vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 callback vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 No vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Lo vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Uu vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 unstable_runWithPriority vendors~main-chunk-93d333ee75638f5125d7.min.js:149587 so vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Uu vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Iu vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 ho vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 unstable_runWithPriority vendors~main-chunk-93d333ee75638f5125d7.min.js:149587 so vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 ho vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 po vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 Au vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 $i vendors~main-chunk-93d333ee75638f5125d7.min.js:149293 pe 208-chunk-3bf09a7292229ace4248.min.js:1 this leads to 400 Bad Request error in request, such as https://<console_route>/api/prometheus/api/v1/query_range?start=1581066557.585&end=1581068357.585&step=60&query=sum%28irate%28container_network_receive_bytes_total%7Bnamespace%3D%7E%22%22%2C+pod%3D%7E%22%22%7D%5B%24interval%5D%29%29+by+%28pod%29&timeout=5s Expected results: 1. No JS errors and other charts can be shown correctly Additional info:
View `k8s-resources-namespace` and `k8s-resources-pod` dashboard, no 'pod is not defined error' error and charts are all displayed very well on page Verified on 4.4.0-0.nightly-2020-02-16-205302
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-2020:0581