Bug 1753091 - "504 Gateway Time-out" for all monitoring routes in http_proxy environment
Summary: "504 Gateway Time-out" for all monitoring routes in http_proxy environment
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.2.0
Assignee: Pawel Krupa
QA Contact: Junqi Zhao
Depends On:
TreeView+ depends on / blocked
Reported: 2019-09-18 05:25 UTC by Junqi Zhao
Modified: 2019-10-16 06:41 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-10-16 06:41:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 482 0 'None' closed Bug 1753091: Inject http_proxy vars 2020-09-22 14:26:12 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:41:45 UTC

Comment 3 Daneyon Hansen 2019-09-18 18:50:48 UTC
See https://bugzilla.redhat.com/show_bug.cgi?id=1752725#c9 for a workaround. https://github.com/openshift/cluster-network-operator/pull/296 is a PR to automatically add the ingress or cluster domain to noProxy. From the PR comments it sounds like this is not desired.

Comment 6 Daneyon Hansen 2019-09-19 21:47:33 UTC
Junqi Zhao, can you add your ingress domain (i.e. apps.wzheng-0917.qe.devcluster.openshift.com) to noProxy to test a workaround to this issue?

Comment 10 errata-xmlrpc 2019-10-16 06:41:33 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.