Bug 1743507

Summary: Should add internal registry address to noProxy globally
Product: OpenShift Container Platform Reporter: XiuJuan Wang <xiuwang>
Component: NetworkingAssignee: Daneyon Hansen <dhansen>
Status: CLOSED ERRATA QA Contact: zhaozhanqi <zzhao>
Severity: high Docs Contact:
Priority: high    
Version: 4.2.0CC: aos-bugs, bparees, gmontero, wewang, wzheng, xtian
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:36:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1743125    

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