-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[2.13] Backport CI fix #7119
[2.13] Backport CI fix #7119
Conversation
Hi @RickHaan. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Btw you can check #7021 to see what was required for 2.14 |
Thanks for your feedback. This is my first time doing a backport. What I will do is discard all my changes locally and then start the cherry-pick from #7021. And force-push my changes to my remote branch so I don't overload your CI (dockerhub limit) with every small change. And then check if I still need stuff from #6957 #6955 #6910 #6962. |
Nice :) I think you can take #6955 at least, it remove about 3 call to dockerhub per jobs (that's ~30 calls per pipeline) |
* fix flake8 errors in Kubespray CI - tox-inventory-builder * fix flake8 errors in Kubespray CI - tox-inventory-builder * Invalidate CRI-O kubic repo's cache Signed-off-by: Victor Morales <v.morales@samsung.com> * add support to configure pkg install retries and use in CI job tf-ovh_ubuntu18-calico (due to it failing often) * Switch Calico and Cilium image repos to Quay.io Co-authored-by: Victor Morales <v.morales@samsung.com> Co-authored-by: Barry Melbourne <9964974+bmelbourne@users.noreply.github.com> Conflicts: roles/download/defaults/main.yml * up vagrant box to fedora/33-cloud-base in cri-o molecule tests (cherry picked from commit 06ec539) * add Google proxy-mirror-cache for docker hub to CI tests (cherry picked from commit d739a6b) * containerd docker hub registry mirror support * containerd docker hub registry mirror support * add docs * fix typo * fix yamllint * fix indent in sample and ansible-playbook param in testcases_run * fix md * mv common vars to tests/common/_docker_hub_registry_mirror.yml * checkout vars to upgrade tests (cherry picked from commit 4a8a52b) * Exclude .git/ from shellcheck If a branch name contains '.sh', current shellcheck checks the branch file under .git/ and outputs error because the format is not shell script one. This makes shellcheck exclude files under .git/ to avoid this issue. (cherry picked from commit e2467d8) Co-authored-by: Hans Feldt <2808287+hafe@users.noreply.github.com> Co-authored-by: Sergey <s.bondarev@southbridge.ru> Co-authored-by: Kenichi Omichi <ken-oomichi@wx.jp.nec.com>
There is too much gap with 2.13 :( you now have an issue with Kube-ovn repository.. Simple way would be to deactivate this test. |
:( I have checked if I could 'fix' it by cherry-picking #6223. But that would require upgrading kube-ovn, which is not a good plan. ( |
You can configure to manual it's enough 👍 |
Signed-off-by: Rick Haan <rickhaan94@gmail.com>
/lgtm |
Thanks for the help with the CI floryut 👍 /assign @Miouge1 |
OK, I guess it doesn't hurt to fix CI in 2.13, but we usually backports only security patches and major bugs. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miouge1, RickHaan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Thanks for your approval. I created the PR since I was running into a CI issue with #7110 . Now that this is merged I will rebase that PR on |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
I am running into two issues with the Kubespray CI with PR-7110.
These issues were fixed in master and backported in 2.14 by @champtar in PR-7021 This PR is meant to backport these fixes into 2.13.
I have cherry-picked these PR's:
* PR-6910* PR-7048* PR-6992Which issue(s) this PR fixes:
Issue with Kubespray CI in PR-7110.
Does this PR introduce a user-facing change?: