Created attachment 1675995 [details] 504 error for prometheus API in console Description of problem: 504 error for prometheus API in console and all targets are down with Kuryr network, see the attached picture. no such error with other network type # oc get network/cluster -oyaml apiVersion: config.openshift.io/v1 kind: Network metadata: creationTimestamp: "2020-04-03T02:32:18Z" generation: 2 name: cluster resourceVersion: "2607" selfLink: /apis/config.openshift.io/v1/networks/cluster uid: c12d517e-585d-45bc-bef1-2a566aec0acd spec: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 externalIP: policy: {} networkType: Kuryr serviceNetwork: - 172.30.0.0/16 status: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 networkType: Kuryr serviceNetwork: - 172.30.0.0/16 all endpoints are down,see the picture, or see from CLI, example: # 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://192.168.0.26:9100/metrics' curl: (7) Failed connect to 192.168.0.26:9100; Connection timed out Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Login admin UI as cluster admin, check "Home -> Overview" page 2. Check targets in prometheus UI 3. Actual results: 504 error for prometheus API in console and all targets are down with Kuryr network Expected results: no error Additional info:
Created attachment 1675996 [details] all targets are down on Prometheus UI
Will verify it after Bug 1825215 is fixed
Tested with 4.4.0-0.nightly-2020-04-21-210658, all targets are UP
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