-
Bug
-
Resolution: Obsolete
-
Undefined
-
None
-
4.16
-
No
-
False
-
Description of problem:
To workaround a problem of oauth2 > 0.15.0 reaching out to the metadata server (169.254.169.254) in environments where traffic to that IP is blocked, we have pinned the oauth2 lib to version 0.15.0. We need to look into either: 1. Reaching out to oauth2 upstream and understand if the introduced change is correct considering containerized workloads. 2. Look into adding `universe_domain` to the GCP creds used by the Installer, to prevent GCP API calls from reaching out to the metadata server.
Version-Release number of selected component (if applicable):
4.16/master
How reproducible:
always
Steps to Reproduce:
1. 2. 3.
Actual results:
golang.org/x/oauth2 is pinned to v0.15.0 google.golang.org/api is pinned to v0.157.0
Expected results:
oauth2 and api libs can be freely updated.
Additional info:
See https://github.com/openshift/cloud-network-config-controller/pull/132
- is related to
-
OCPBUGS-30642 [GCP] GCP installs are permafailing because of oauth2 bump
- Closed