+++ This bug was initially created as a clone of Bug #1825207 +++ 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: --- Additional comment from Junqi Zhao on 2020-04-17 12:03:22 UTC ---
Verified in 4.4.0-0.nightly-2020-05-08-224132 on top of OSP 16 compose RHOS_TRUNK-16.0-RHEL-8-20200506.n.2 (with OVS and amphora-driver). OCP 4.4 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.46:9100/metrics'
Created attachment 1687321 [details] GET requests from console GUI to prometheus API
Created attachment 1687322 [details] "Monitoring -> Metrics" menu from console GUI
Created attachment 1687323 [details] kube_pod_info_node_count 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:2133