Test-infra: go get kubetest failing with "unable to access 'https://git.apache.org/thrift.git/'"

Created on 2 Sep 2019 · 12Comments · Source: kubernetes/test-infra

What happened:
To solve failures of openstack conformance test, i followed the approach from here
https://github.com/kubernetes/test-infra/issues/14070#issuecomment-525651839

i tried to install kubetest
export GO111MODULE=on go get -u k8s.io/test-infra/kubetest
but it is failing with error
go: git.apache.org/[email protected]: git fetch -f https://git.apache.org/thrift.git refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/ubuntu/go/pkg/mod/cache/vcs/83dba939f95a790e497d565fc4418400145a1a514f955fa052f662d56e920c3e: exit status 128: fatal: unable to access 'https://git.apache.org/thrift.git/': Failed to connect to git.apache.org port 443: Connection timed out go get: error loading module requirements
What you expected to happen:
go get -u k8s.io/test-infra/kubetest, should run successfully

How to reproduce it (as minimally and precisely as possible):

Please provide links to example occurrences, if any:

Anything else we need to know?:

kinbug

Source

adisky

👍2

Most helpful comment

Please use a proxy to download deps, which you can do by either:

Using go 1.13 (which enables this by default), and/or
export GOPROXY=https://proxy.golang.org && export GOSUMDB=sum.golang.org && export GO111MODULE=on

fejta on 3 Sep 2019

🚀6

All 12 comments

I also found this, while searching for the issue
https://github.com/jenkins-x/jx/issues/3320

adisky on 2 Sep 2019

/assign @fejta

adisky on 2 Sep 2019

fisherxu on 2 Sep 2019

also met this error

fisherxu on 2 Sep 2019

same error

gaopenghigh on 3 Sep 2019

same on our side.
We experience this since friday.
Looks like apache is still investigating this issue on their side: https://status.apache.org/

schrodit on 3 Sep 2019

Updates from SIG-testing slack channel ( https://kubernetes.slack.com/archives/C09QZ4DQB/p1567498382002500 ):

yeah they moved to github, we have the same problem on tekton, simplest fix is : https://github.com/tektoncd/cli/pull/260/files (without the need to rename imports)

and there is no problem in the build running in CI, wondering why problem in our env

CI sets GOPROXY=https://proxy.golang.org globally iirc, meaning the go module cache is probably saving you..

Fix was proposed in https://github.com/kubernetes/test-infra/pull/14173

alejandrox1 on 3 Sep 2019

Please use a proxy to download deps, which you can do by either:

Using go 1.13 (which enables this by default), and/or
export GOPROXY=https://proxy.golang.org && export GOSUMDB=sum.golang.org && export GO111MODULE=on

fejta on 3 Sep 2019

🚀6

Had same error yesterday , make sure GO111MODULE=on so that new modules can be downloaded

dpandhi-git on 4 Sep 2019

Please use a proxy to download deps, which you can do by either:

Using go 1.13 (which enables this by default), and/or

export GOPROXY=https://proxy.golang.org && export GOSUMDB=sum.golang.org && export GO111MODULE=on

@fejta Thanks, we are able to run kubetest with above settings

adisky on 4 Sep 2019

iirc this has been resolved. But please feel free to reopen otherwise.
/close

alejandrox1 on 20 Sep 2019

@alejandrox1: Closing this issue.

In response to this:

iirc this has been resolved. But please feel free to reopen otherwise.
/close

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.