-
Notifications
You must be signed in to change notification settings - Fork 2.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
kubekins-e2e:v20201225-59e70a3-master used in test contains WIP code that is not submitted #20403
Comments
I triggered a build of It has finished now:
Can you help me with releasing this? |
Or we can use 'gcr.io/k8s-testimages/bootstrap:v20210108-5927ee692c' which includes submitted #20276 |
These logs don't exist. Please provide a deck link (something that uploads to GCS, not grabbing from the apiserver) and reopen. |
Also please note:
Finally the most recent versions of these jobs https://testgrid.k8s.io/google-gce#gce-cos-master-scalability-100 no longer use this commit: https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-scalability/1347598028030087168 shows https://prow.k8s.io/view/gcs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce-scalability/1347660928375590912 shows |
Thanks, it seems to be OK now. We know that bootstrap.py is deprecated, the work I'm doing is to unblock migration out of bootstrap (see #20275). |
What happened:
When I was reading logs for https://prow.k8s.io/log?container=test&id=1347195315899338752&job=ci-kubernetes-e2e-gci-gce-scalability I noticed that it starts with:
Those lines are a part of #20273 PR I was playing with last month. For some reason this has been included in kubekins-e2e image, without being submitted.
What you expected to happen:
Not submitted code is not included in live kubekins-e2e image.
How to reproduce it (as minimally and precisely as possible):
Please provide links to example occurrences, if any:
https://prow.k8s.io/log?container=test&id=1347195315899338752&job=ci-kubernetes-e2e-gci-gce-scalability
Anything else we need to know?:
Most likely, my experimental bootstrap image has been included in the kubekins-e2e build (I'm sorry for that, I haven't expected that any bootstrap image can be included, I expected rather a process where some automatic tool builds new bootstrap image from known state).
@fejta @chases2 @kadirselcuk
How to fix that?
I'm thinking about triggering new bootstrap image build (with master), then update kubekins-e2e.
The text was updated successfully, but these errors were encountered: