-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
False
-
-
False
-
None
-
None
-
None
-
None
-
None
level=info msg=Credentials loaded from environment variable "GOOGLE_CLOUD_KEYFILE_JSON", file "/var/run/secrets/ci.openshift.io/cluster-profile/gce.json" level=error msg=failed to fetch Master Machines: failed to load asset "Install Config": failed to create install config: <nil>: Internal error: failed to create compute service: Get "http://169.254.169.254/computeMetadata/v1/universe/universe_domain": dial tcp 169.254.169.254:80: connect: connection refused
Details in https://redhat-internal.slack.com/archives/CEKNRGF25/p1709812331857849
Believe it was introduced via https://github.com/openshift/installer/pull/8020 which bumped google sdk.
We block traffic from cluster-networked pods to the metadata ip. The latest google sdk will try to get the universe_domain from the metadata server if it is not set in the credentials
A revert is up but still working through issues