Created attachment 1679633 [details] 504 error for the Prometheus APIs for "Home -> Overview" page Created attachment 1679633 [details] 504 error for the Prometheus APIs for "Home -> Overview" page Description of problem: This bug is from Bug 1822861, use it to track the 504 error for the Prometheus APIs in the administrator console. Login the administrator console, check in "Home -> Overview" page, "Monitoring -> Alerting", or "Monitoring -> Metrics" page, the Prometheus APIs in the administrator console returns 504 error in the kuryr OCP 4.5.0-0.nightly-2020-04-17-053057 cluster, see the attached picture Version-Release number of selected component (if applicable): kuryr OCP 4.5.0-0.nightly-2020-04-17-05305 How reproducible: always Steps to Reproduce: 1. See the description 2. 3. Actual results: 504 error for Prometheus API in administrator console Expected results: no error Additional info:
Created attachment 1679637 [details] failed to load metrics list due to 504 error
Verified in 4.5.0-0.nightly-2020-04-29-144201 on top of RHOS_TRUNK-16.0-RHEL-8-20200427.n.0 OSP 16 compose. OSP 16 deployment with OVS neutron backend. OCP 4.5 installation with Kuryr completed successfully. There are no 504 error responses to Prometheus metrics requests in the GUI "Home -> Overview" page. The metrics are retrieved correctly in "Monitoring -> Metrics" The metrics can be retrieved from the CLI as well: $ token=`oc sa get-token prometheus-k8s -n openshift-monitoring` $ oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://10.196.2.22:9100/metrics'
Created attachment 1683314 [details] GET requests from console GUI to prometheus API
Created attachment 1683315 [details] "Monitoring -> Metrics" menu from console GUI
Created attachment 1683316 [details] kube_pod_info_node_coun metric retrieval from console GUI
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:2409