-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DefaultCredentialsError after Compute Engine Metadata server failures #814
Comments
I have seen this as a recommended solution but this is not possible for us at this time. Looking for a fix to the root cause here (metadata server issues) |
I am not sure what the latest recommendations are around the Metadata server - @arithmetic1728 @silvolu Could you take a look? |
Any update here? |
Any update regarding this issue? |
Probably you can create a global credential using |
Good one. Thanks @arithmetic1728 |
Still seeing the same issue mentioned in #211
Environment details
google-auth
version: 1.33.0Steps to reproduce
cred, _ = default(scopes=scopes)
fails after successfully running for a prolonged periodContext:
I'm running a python multiprocessing service inside a docker container in Google's Container-Optimized OS (cos-stable-89-16108-470-1). The processes typically run bigquery queries that it consumes from pubsub topics and sends logs to other pubsub topics. The default authentication from the google-auth package works fine for some time (typically ~18 hours) while the processes continuously run bigquery commands and eventually fail on connecting to the Compute Engine Metadata server that results in DefaultCredentialsError (along with other google connection errors).
Tracebacks:
This previously reported issue (#211) has mentioned the same errors but the thread was closed after pushing fixes to later versions. Hence opening a new issue now since i'm still seeing these errors in the latest version.
The text was updated successfully, but these errors were encountered: