openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.49k stars 4.7k forks source link

Failed to setup provider config for "gce" #26588

Closed jianzhangbjz closed 2 years ago

jianzhangbjz commented 3 years ago

[provide a description of the issue] Failed to find the GCE credentials,

Nov 10 15:03:44.740: INFO: Fetching cloud provider for "gce"
E1110 15:03:44.745853   71864 test_context.go:500] Failed to setup provider config for "gce": Error building GCE/GKE provider: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
Version

[provide output of the openshift version or oc version command]

mac:origin jianzhang$ oc version
Client Version: 4.10.0-0.nightly-2021-11-09-050826
Server Version: 4.10.0-0.nightly-2021-11-04-001635
Kubernetes Version: v1.22.1+1b2affc
Steps To Reproduce
  1. [step 1]
  2. [step 2]
Current Result
mac:origin jianzhang$ ./openshift-tests run all --dry-run|grep "OLM version"|./openshift-tests run -f -
openshift-tests version: v4.1.0-4519-gc55480f
started: (0/1/1) "[sig-arch] ocp payload should be based on existing source OLM version should contain the source commit id [Suite:openshift/conformance/parallel]"

Nov 10 14:49:23.261: INFO: Fetching cloud provider for "gce"
E1110 14:49:23.394405   71711 test_context.go:500] Failed to setup provider config for "gce": Error building GCE/GKE provider: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.

failed: (7.2s) 2021-11-10T06:49:23 "[sig-arch] ocp payload should be based on existing source OLM version should contain the source commit id [Suite:openshift/conformance/parallel]"

Timeline:

Nov 10 14:49:16.140 - 9s    W alert/AlertmanagerReceiversNotConfigured ns/openshift-monitoring ALERTS{alertname="AlertmanagerReceiversNotConfigured", alertstate="firing", namespace="openshift-monitoring", prometheus="openshift-monitoring/k8s", severity="warning"}
Nov 10 14:49:16.140 - 9s    W alert/CannotRetrieveUpdates node/10.0.0.4:9099 ns/openshift-cluster-version pod/cluster-version-operator-57d9dff759-8vg69 ALERTS{alertname="CannotRetrieveUpdates", alertstate="firing", endpoint="metrics", instance="10.0.0.4:9099", job="cluster-version-operator", namespace="openshift-cluster-version", pod="cluster-version-operator-57d9dff759-8vg69", prometheus="openshift-monitoring/k8s", service="cluster-version-operator", severity="warning"}
Nov 10 14:49:16.140 - 9s    E alert/Watchdog ns/openshift-monitoring ALERTS{alertname="Watchdog", alertstate="firing", namespace="openshift-monitoring", prometheus="openshift-monitoring/k8s", severity="none"}
Nov 10 06:49:16.156 I e2e-test/"[sig-arch] ocp payload should be based on existing source OLM version should contain the source commit id [Suite:openshift/conformance/parallel]" started
Nov 10 06:49:16.156 - 7s    E e2e-test/"[sig-arch] ocp payload should be based on existing source OLM version should contain the source commit id [Suite:openshift/conformance/parallel]" e2e test finished As "Failed"
Nov 10 06:49:23.401 E e2e-test/"[sig-arch] ocp payload should be based on existing source OLM version should contain the source commit id [Suite:openshift/conformance/parallel]" finishedStatus/Failed

Flaky invariants:

[sig-arch] Monitor cluster while tests execute

Failing tests:

[sig-arch] ocp payload should be based on existing source OLM version should contain the source commit id [Suite:openshift/conformance/parallel]

error: 1 fail, 0 pass, 0 skip (7.3s)
Expected Result

Run it well on GCP.

Additional Information

[try to run $ oc adm diagnostics (or oadm diagnostics) command if possible] [if you are reporting issue related to builds, provide build logs with BUILD_LOGLEVEL=5] [consider attaching output of the $ oc get all -o json -n <namespace> command to the issue] [visit https://docs.openshift.org/latest/welcome/index.html]

jianzhangbjz commented 2 years ago

Close it since I think I can get the creds from the cluster's secret, like

[cloud-user@preserve-olm-env jian]$ oc get secret gcp-credentials -o yaml -n kube-system
apiVersion: v1
data:
service_account.json: ...
...