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
CI Periodic jobs not testing recent kops builds #16533
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
This was referenced May 7, 2024
Merged
This has been fixed |
@rifelpet: Closing this issue. 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-sigs/prow repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
/kind bug
There's multiple issues with the kops pipeline that allow periodic jobs to pick up new kops builds.
Observe these two periodic jobs from weeks apart:
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/e2e-kops-aws-arm64-ci/1787557790076637184
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/e2e-kops-aws-arm64-ci/1781518104833036288
Both download the same CI version marker:
The marker itself hasn't been modified since March
The updown job that normally updates this has been failing for as far back as testgrid history shows:
https://testgrid.k8s.io/kops-latest#kops-aws-updown
The postsubmit job has also been failing for a few weeks for all merges on the master branch (release branches are working)
https://testgrid.k8s.io/sig-cluster-lifecycle-kops#kops-postsubmit-push-to-staging
We should fix this and keep an eye on the impact to periodic jobs before cutting the new releases.
The text was updated successfully, but these errors were encountered: