-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
storage: timeout for /computeMetadata/v1/universe/universe_domain in storage.NewClient #9350
storage: timeout for /computeMetadata/v1/universe/universe_domain in storage.NewClient #9350
Comments
@jaimem88 Thank you for reporting this bug. I will try to reproduce it today. |
@jaimem88 I have been unable to reproduce it so far. The request that times out according to your logs is to the Compute Metadata Server. It should only be made if the default credentials are determined to be provided by the Compute Metadata Server. Just from static inspection (ie, looking) the bug appears to be in this line. |
Do you know if your CI runs on GCE and if so, exactly which GCE-based product? (GKE, Cloud Run?). It seems |
Can you provide the full |
Thanks for looking into this @quartzmo!
Here are the full
I believe our Just for reference, the same job on the previous version |
@jaimem88 Are you still seeing this issue? If so, would it be possible for you to run the following The commands are almost identical, the difference is just IP address vs domain name. As you can see from the IP address, the URL in your logs is correct. It is not supposed to timeout, but the rollout of this feature seems to possibly be inconsistent. Otoh, the timeout might have been a rare transient issue such as a restart. Thank you!
|
* Temporarily return googleapis.com on MDS universe_domain timeout. closes: googleapis/google-cloud-go#9350
…#2393) * Temporarily return googleapis.com on MDS universe_domain timeout. closes: googleapis/google-cloud-go#9350
@jaimem88 Please upgrade to https://github.com/googleapis/google-api-go-client/releases/tag/v0.162.0 if possible, and let us know if the error is resolved. |
Thank you @quartzmo! The latest version works as before https://gitlab.com/gitlab-org/container-registry/-/jobs/6111764468 🎉 |
We are experiencing this issue upgrading logging from 0.7.0 to 0.9.0 |
@clerk-zach Did you try the above workaround? |
Environment details
Steps to reproduce
The latest update is breaking our pipeline when we try to update the library:
https://gitlab.com/gitlab-org/container-registry/-/merge_requests/1569.
One of our integration tests keeps failing as seen in this CI job.
This seems suspiciously related to googleapis/google-api-go-client@b21a1fa. I am not sure where the hostname is coming from but it seems that the
DefaultEndpoint
is not being set properly.The text was updated successfully, but these errors were encountered: