GCP: Failed to get regions list

[kramhuber]

What happened?

We were seeing this warning on every preview/up with Neo using v9. It didn't seem to affect anything, it was just noisy.

warning: failed to get regions list: failed to create compute service: credentials: could not find default credentials. See https://cloud.google.com/docs/authentication/external/set-up-adc for more information

Example

Run an up or preview using OIDC creds from ESC and examine the preview/up logs. We were specifically creating GKE clusters with gpu nodes.

Output of pulumi about

NA

Additional context

Reach out to @kramhuber, @flostadler, or @mikhailshilkov for more details

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[guineveresaenger]

Hi @kramhuber - thank you for reporting this. Could you please send us the sample program so we can quickly duplicate the behavior?

A few questions:

• does this happen on every pulumi up for every resource you've tried? Or is it specific to a GKE cluster? (Asking because clusters take more time to provision and if this can be repro'ed with a simpler resource).
• does the warning happen only when using ESC creds?
• do you know whether it happens prior to v9, as in, is this new behavior?
• when you say "examine the preview/up logs" - do you mean this warning pops up in the details?
• perhaps silly: does this happen only when Neo runs the commands for you?

Thank you!

[kramhuber]

does this happen on every pulumi up for every resource you've tried? Or is it specific to a GKE cluster?

Yep, we were seeing it on every up with GKE; could be causation/correlation, but I'm fairly certain GKE was the cause

does the warning happen only when using ESC creds?

I was only using ESC creds, so hard to say; ESC + GCP provider was @flostadler's hypothesis

do you know whether it happens prior to v9, as in, is this new behavior?

I was only using v9, so unsure on earlier versions

do you mean this warning pops up in the details

Yep, exactly.

does this happen only when Neo runs the commands for you?

Yeah -- unsure causation/correlation because that's all I was using