Bug 1754049

Summary: [proxy] Need to add "metadata.google.internal." to noProxy list on GCP
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: NetworkingAssignee: Daneyon Hansen <dhansen>
Networking sub component: openshift-sdn QA Contact: Gaoyun Pei <gpei>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: adahiya, bbennett, dhansen, gpei, scuppett, wking
Version: 4.2.0Keywords: TestBlocker
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1753930
: 1759251 1759253 (view as bug list) Environment:
Last Closed: 2020-01-23 11:06:39 UTC Type: ---
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: 1759251, 1759253    

Comment 3 W. Trevor King 2019-09-27 05:17:51 UTC
Installer bug does not block this one; they both need to land before either can be VERIFIED.

Comment 6 Daneyon Hansen 2019-10-07 17:14:10 UTC
*** Bug 1759251 has been marked as a duplicate of this bug. ***

Comment 8 Gaoyun Pei 2019-10-09 02:50:29 UTC
Move this bug to verified according to https://bugzilla.redhat.com/show_bug.cgi?id=1753930#c16

"metadata,metadata.google.internal,metadata.google.internal." was added into default noProxy list
# oc get proxy cluster -o jsonpath='{.status.noProxy}' --config=/var/opt/openshift/auth/kubeconfig
.cluster.local,.svc,10.0.0.0/16,10.128.0.0/14,127.0.0.1,169.254.169.254,172.30.0.0/16,api-int.qe-gpei-4303.qe.gcp.devcluster.openshift.com,etcd-0.qe-gpei-4303.qe.gcp.devcluster.openshift.com,etcd-1.qe-gpei-4303.qe.gcp.devcluster.openshift.com,etcd-2.qe-gpei-4303.qe.gcp.devcluster.openshift.com,localhost,metadata,metadata.google.internal,metadata.google.internal.,test.no-proxy.com

Comment 10 errata-xmlrpc 2020-01-23 11:06:39 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-2020:0062