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

test ci-kubernetes-e2e-kind-compatibility-versions failing w/ could not find Kubernetes source under current working directory or GOPATH #33591

Closed
aaron-prindle opened this issue Oct 7, 2024 · 2 comments · Fixed by #33592
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.

Comments

@aaron-prindle
Copy link
Contributor

What happened:
Newly added periodic test - ci-kubernetes-e2e-kind-compatibility-versions is failing (related PR: #33534)

What you expected to happen:
I expected the test to pass. This is the first submission for the test and it seems there is some missing initialization

How to reproduce it (as minimally and precisely as possible):
I don't believe there is a simple way to reproduce running a prow job locally. You can trigger the prow test directly or look at the prow logs to see the failing job

Please provide links to example occurrences, if any:
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-kind-compatibility-versions/1843359973241786368

exported KUBECONFIG=/root/.kube/kind-test-config
+ kind version
kind v0.25.0-alpha+b404897ff06f98 go1.22.6 linux/amd64
+ build
+ kind build node-image -v 1
ERROR: error building node image: error finding kuberoot: could not find Kubernetes source under current working directory or GOPATH=/home/prow/go
@aaron-prindle aaron-prindle added the kind/bug Categorizes issue or PR as related to a bug. label Oct 7, 2024
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Oct 7, 2024
@aaron-prindle
Copy link
Contributor Author

/assign
/sig api-machinery

@k8s-ci-robot k8s-ci-robot added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 7, 2024
@BenTheElder
Copy link
Member

BenTheElder commented Oct 7, 2024

we have two good options: https://github.com/kubernetes/test-infra/pull/33534/files#r1790765481

the least work is adding kubernetes to the extra refs

slightly more work but cheaper/faster would be reworking the script to use something like KUBE_LATEST_VERSION="$(curl -L 'https://dl.k8s.io/ci/latest')"; kind build node-image 'https://dl.k8s.io/ci/'"${KUBE_LATEST_VERSION}"; # fetch the e2e.test etc from releases in the script

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery.
Projects
None yet
3 participants