Created attachment 1605937 [details] proxy Description of problem: console get error on polling promethus data against proxy enablement cluster Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-08-18-054211 How reproducible: Always Steps to Reproduce: 1. create resources under a project 2.Check workload->pod page, project->detail page, compute->node page 3. Actual results: All chart shows 'no datapoints found' and promethus query request got 502 502 Bad Gateway Expected results: should polling promethus data as expected. Additional info: see attachment
Created attachment 1605938 [details] 502 Bad Gateway for Alerts/Silences same "502 Bad Gateway" to list Alerts/Silences
Created attachment 1605943 [details] access log "prometheus-k8s.openshift-monitoring.svc:9091" and "prometheus-k8s.openshift-monitoring.svc:9092" are accessed via the proxy
We need to make sure no services are accessed through the proxy, only the OAuth server.
See also https://github.com/openshift/console/issues/2435
https://github.com/openshift/cluster-network-operator/pull/295 adds `.svc` to the no proxy list, which should address this problem.
Now console can poll data from promethus service on clusters with proxy Verified this bug 4.2.0-0.nightly-2019-08-23-004712
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-2019:2922