[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ocp4 cluster fails to initialize on GCP



On Tue, Oct 8, 2019 at 4:18 PM Just Marvin wrote:
> Oct 06 11:00:34 ....E1006 11:00:34.444173    1201 aws_credentials.go:77] while getting AWS credentials NoCredentialProviders: no valid providers in chain. Deprecated.
> Oct 06 11:00:34 ....         For verbose messaging see aws.Config.CredentialsChainVerboseErrors
>
>     Is this a potential cause of my problems or an unrelated issue?

I think it's unrelated.  For example, in logs from a successful 4.2
GCP CI run [1]:

$ curl -s https://storage.googleapis.com/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade-4.2/84/artifacts/e2e-gcp-upgrade/must-gather/registry-svc-ci-openshift-org-ocp-4-2-2019-10-08-125557-sha256-72d3b1b48fd0c2b518b0ef7e681aad61429a7a27efec5b2faa48bc301cb65480/host_service_logs/masters/kubelet_service.log
| grep provider | head -n8
Oct 08 21:33:42 ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
hyperkube[1166]: I1008 21:33:42.033290    1166 flags.go:33] FLAG:
--cloud-provider="gce"
Oct 08 21:33:42 ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
hyperkube[1166]: I1008 21:33:42.033781    1166 flags.go:33] FLAG:
--provider-id=""
Oct 08 21:33:42 ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
hyperkube[1166]: W1008 21:33:42.066891    1166 plugins.go:118]
WARNING: gce built-in cloud provider is now deprecated. The GCE
provider is deprecated and will be removed in a future release
Oct 08 21:33:42 ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
hyperkube[1166]: I1008 21:33:42.338212    1166 server.go:545]
Successfully initialized cloud provider: "gce" from the config file:
""
Oct 08 21:33:42 ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
hyperkube[1166]: I1008 21:33:42.338301    1166 server.go:893] cloud
provider determined current node name to be
ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
Oct 08 21:33:42 ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
hyperkube[1166]: I1008 21:33:42.372724    1166 server.go:893] cloud
provider determined current node name to be
ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
Oct 08 21:33:42 ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
hyperkube[1166]: I1008 21:33:42.374156    1166 kubelet.go:395] cloud
provider determined current node name to be
ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
Oct 08 21:33:42 ci-op--mj9nc-m-1.c.openshift-gce-devel-ci.internal
hyperkube[1166]: E1008 21:33:42.390539    1166 aws_credentials.go:77]
while getting AWS credentials NoCredentialProviders: no valid
providers in chain. Deprecated.

We're still using the built-in cloud providers at the moment, and the
AWS provider being grumpy is unlikely to be a problem on GCP.

Cheers,
Trevor

[1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-gcp-upgrade-4.2/84


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]