Bug 2044289 - [4.8]504 error for Prometheus API in administrator console with kuryr network
Summary: [4.8]504 error for Prometheus API in administrator console with kuryr network
Keywords:
Status: CLOSED DUPLICATE of bug 2019980
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Michał Dulko
QA Contact: Jon Uriarte
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-24 11:21 UTC by Junqi Zhao
Modified: 2022-02-08 15:50 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-02 12:37:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
"Home -> Overview" page, 504 error (413.52 KB, image/png)
2022-01-24 11:21 UTC, Junqi Zhao 		no flags Details
View All

Description Junqi Zhao 2022-01-24 11:21:33 UTC 
Created attachment 1853054 [details]
"Home -> Overview" page, 504 error

Description of problem:
UPI OpenStack cluster with Kuryr network
# oc get network/cluster -o jsonpath="{.spec.networkType}"
Kuryr

# oc get infrastructures/cluster -o jsonpath="{.spec.platformSpec.type}"
OpenStack

Login the administrator console.
1. check in "Home -> Overview" page, "Cluster utilization" section, result for CPU/Memory and etc is "No datapoints found.", error is: Failed to load resource: the server responded with a status of 504 (Gateway Time-out)
2.  "Monitoring -> Alerting", or "Monitoring -> Metrics" page, the Prometheus APIs in the administrator console returns 504 error in the kuryr OCP 4.8.0-0.nightly-2022-01-19-104449 cluster

Version-Release number of selected component (if applicable):
4.8.0-0.nightly-2022-01-19-104449

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:
Note You need to log in before you can comment on or make changes to this bug.