-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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.googleapis.com flake: network unreachable #10162
Comments
Are you sure that's yum and not your curl command? To me it looks like yum was successful but downloading golang binaries was not. |
Yeah, that's the curl command, ip address is in google's netblock and is a near match to what storage.googleapis.com resolves to from my workstation.
|
@sdodson good catch -- the question remains, can we mitigate this at all or is this just one of those transient network things we're just going to have to live with? |
golang could be installed into the images minimizing the number of times you attempt to pull it. I don't know enough about the context to give you solid advice here. |
We'll wait for @smarterclayton's test containers to embed Golang. |
@stevekuznetsov this issue seems to have recurred quite a few times since it was closed. |
/reopen |
@Kargakis: you can't re-open an issue unless you authored it or you are assigned to it. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'd have to check but I can't think of any place we're building |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
Seen here
@cgwalters @tdawson @sdodson is there anything we can realistically do here?
The text was updated successfully, but these errors were encountered: