Bug 1743507 - Should add internal registry address to noProxy globally
Summary: Should add internal registry address to noProxy globally
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2.0
Assignee: Daneyon Hansen
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks: 1743125
TreeView+ depends on / blocked
 
Reported: 2019-08-20 07:20 UTC by XiuJuan Wang
Modified: 2019-10-16 06:37 UTC (History)
6 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:37:22 UTC

Comment 1 Ben Parees 2019-08-20 17:45:32 UTC 
the entire internal service domain should be in noproxy, not just the registry service.
Comment 2 Daneyon Hansen 2019-08-20 20:17:50 UTC 
https://github.com/openshift/cluster-network-operator/pull/295 submitted to fix this bug. Checking with installer team to see if Installer needs a similar fix
Comment 5 XiuJuan Wang 2019-08-22 05:39:16 UTC 
This issue has been fixed in version 4.2.0-0.nightly-2019-08-21-235427 

$oc get proxy cluster -o json  |  jq .status
{
  "httpProxy": "http://proxy-user1:*********:3128",
  "httpsProxy": "http://proxy-user1:*********139.178.76.57:3128",
  "noProxy": ".cluster.local,.svc,10.128.0.0/14,127.0.0.1,172.30.0.0/16,api-int.qe-xiuwang-proxy-821.qe.devcluster.openshift.com,api.qe-xiuwang-proxy-821.qe.devcluster.openshift.com,compute-0,control-plane-0,etcd-0.qe-xiuwang-proxy-821.qe.devcluster.openshift.com,localhost"
}
Comment 6 errata-xmlrpc 2019-10-16 06:36:35 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.

https://access.redhat.com/errata/RHBA-2019:2922
Note You need to log in before you can comment on or make changes to this bug.