Skip to content
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

Closed
stevekuznetsov opened this issue Aug 2, 2016 · 12 comments
Closed

storage.googleapis.com flake: network unreachable #10162

stevekuznetsov opened this issue Aug 2, 2016 · 12 comments
Assignees
Labels
area/infrastructure kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2

Comments

@stevekuznetsov
Copy link
Contributor

Loaded plugins: fastestmirror, ovl
Cleaning repos: base epel extras updates
Cleaning up everything
Cleaning up list of fastest mirrors
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0
  0     0    0     0    0     0      0      0 --:--:--  0:00:03 --:--:--     0
  ...
  0     0    0     0    0     0      0      0 --:--:--  0:02:07 --:--:--     0
curl: (7) Failed to connect to 2607:f8b0:400d:c01::80: Network is unreachable

gzip: stdin: unexpected end of file
tar: Child returned status 1
tar: Error is not recoverable: exiting now
error: running '/bin/sh -c export "VERSION=1.6" "GOARM=5" "GOPATH=/go" "GOROOT=/usr/local/go" "OS_VERSION_FILE=/go/src/github.com/openshift/origin/os-version-defs" "TMPDIR=/openshifttmp" "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/go/bin"; mkdir $TMPDIR &&     INSTALL_PKGS="make gcc zip mercurial krb5-devel bsdtar" &&     yum install -y $INSTALL_PKGS &&     rpm -V $INSTALL_PKGS &&     yum clean all &&     curl https://storage.googleapis.com/golang/go$VERSION.linux-amd64.tar.gz | tar -C /usr/local -xzf - &&     go get golang.org/x/tools/cmd/cover github.com/tools/godep github.com/golang/lint/golint &&     touch /os-build-image' failed with exit code 2
[ERROR] PID 15978: hack/build-base-images.sh:27: `'/data/src/github.com/openshift/origin/_output/local/bin/linux/amd64/oc' ex dockerbuild /data/src/github.com/openshift/origin/images/release openshift/origin-release` exited with status 1.
[INFO]      Stack Trace: 
[INFO]        1: hack/build-base-images.sh:27: `'/data/src/github.com/openshift/origin/_output/local/bin/linux/amd64/oc' ex dockerbuild /data/src/github.com/openshift/origin/images/release openshift/origin-release`
[INFO]        2: hack/build-base-images.sh:33: build
[INFO]   Exiting with code 1.

Seen here

@cgwalters @tdawson @sdodson is there anything we can realistically do here?

@stevekuznetsov stevekuznetsov added kind/test-flake Categorizes issue or PR as related to test flakes. area/infrastructure labels Aug 2, 2016
@sdodson
Copy link
Member

sdodson commented Aug 2, 2016

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.

@sdodson
Copy link
Member

sdodson commented Aug 2, 2016

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.

$ host storage.googleapis.com
storage.googleapis.com is an alias for storage.l.googleusercontent.com.
storage.l.googleusercontent.com has address 209.85.232.128
storage.l.googleusercontent.com has IPv6 address 2607:f8b0:400d:c0d::80

@stevekuznetsov stevekuznetsov changed the title yum flake: network unreachable storage.googleapis.com flake: network unreachable Aug 2, 2016
@stevekuznetsov
Copy link
Contributor Author

@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?

@sdodson
Copy link
Member

sdodson commented Aug 2, 2016

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.

@stevekuznetsov
Copy link
Contributor Author

We'll wait for @smarterclayton's test containers to embed Golang.

@0xmichalis
Copy link
Contributor

@stevekuznetsov this issue seems to have recurred quite a few times since it was closed.

@0xmichalis
Copy link
Contributor

/reopen

@openshift-ci-robot
Copy link

@Kargakis: you can't re-open an issue unless you authored it or you are assigned to it.

In response to this:

/reopen

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.

@0xmichalis 0xmichalis reopened this Jul 20, 2017
@stevekuznetsov
Copy link
Contributor Author

I'd have to check but I can't think of any place we're building openshift/release today... At least we shouldn't be

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 15, 2018
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 18, 2018
@openshift-bot
Copy link
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infrastructure kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P2
Projects
None yet
Development

No branches or pull requests

6 participants