Error getting token from client GCP session: Could not automatically determine credentials. Please set GOOGLE_APPLICATION_CREDENTIALS

[rsignell]

I'm getting this "error" every time I fire up a Coiled cluster. I've got gcsfs in my "pangeo" software environment, but it's just in there to access public data from Google Cloud Storage -- I don't have any credentials to set.

Is there some way to gracefully avoid this issue?

[dchudz]

Sorry for the delay here, Rich.

Can you clarify: Is this error blocking some computation you want to do? Or is it just that the error is annoying to see in your logs?

[rsignell]

@dchudz Doesn't affect anything. Just mentioning it because I was teaching a short course and I have to then spend time telling the students that it's nothing to worry about and why it's likely popping up

[dchudz]

Hm, yeah, sorry about this. This behavior is triggered by having google-auth installed (which is a dependency of gcsfs).

I think we could at least make the warning a little less scary, but it may be useful to keep some kind of warning for people who do expect credentials to be set.

[rsignell]

Okay, I guess we could also set some bogus credential env vars

[rsignell]

@dchudz I removed gcsfs from the Coiled environment:
https://cloud.coiled.io/software/alias/91580/account/esip-lab/build/84676?workspace=esip-lab

and I'm still getting this warning. I do have gcsfs in the client environment, but that doesn't matter if I'm requesting the Coiled software environment by name, right?

What other package be triggering it?
(I'm doing a demo next week at the ESIP Summer Meeting and this message is annoying)

[dchudz]

The warning is based on the client environment.

The presence of gcfs in the client is making Coiled think you want us to send Google credentials, but we can't.

In response to this discussion I did change the warning to be less scary. It should say something like "Could not get token from client GCP session. This is not a concern unless you're planning to use forwarded GCP credentials on your cluster. ...".

It looks to me like you're already on the latest client version, so you should be getting that less scary version of the warning. It's still a problem for you though?

Can you remove gcsfs from the client environment?