-
Notifications
You must be signed in to change notification settings - Fork 123
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
fix,pre-pull-images: use pre-generated image lists for pre-pull #1374
base: main
Are you sure you want to change the base?
Conversation
Skipping CI for Draft Pull Request. |
/test |
@dhiller: The
The following commands are available to trigger optional jobs:
Use
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. |
/test check-provision-k8s-1.32 |
483f345
to
38115f0
Compare
/test check-provision-k8s-1.32 |
38115f0
to
1019d09
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
1019d09
to
3e7c641
Compare
/test check-provision-k8s-1.32 |
/hold waiting for kubevirt/project-infra#3948 |
updating images through kubevirt/project-infra#3949 |
/unhold |
/test check-provision-k8s-1.32 |
since the manifests are not inside the cluster deploy directory any more they are not being copied into the directory any more, thus the fetch-images.sh will not find any images. Therefore we move the fetch-images.sh into the main provision/k8s folder and replace the per version with a pre-pull-images text file. This file needs to get updated whenever the manifests inside either the k8s version folder or the manifests inside the gocli change. Thus we also create a script update-pre-pull-images.sh and call that whenever the cluster is checked at first. Signed-off-by: Daniel Hiller <[email protected]>
3e7c641
to
d80ea5a
Compare
/test check-provision-k8s-1.32 |
@brianmcarey I think I have it working now :) |
Hm, strange, on all the check-provision the same test fails: Any ideas? |
/test check-provision-1.30 |
@dhiller: The specified target(s) for
The following commands are available to trigger optional jobs:
Use
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. |
/test check-provision-k8s-1.30 |
@dhiller: The following tests failed, say
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. I understand the commands that are listed here. |
What this PR does / why we need it:
Detection of missing pre-pulled images broke when the provisioning was moved into gocli. Therefore we change from calling
fetch-images.sh
at runtime to a generatedpre-pull-images
file.Changes in this PR:
update-pre-pull-images.sh
generatespre-pull-images
, callingfetch-images.sh
, which is moved from the version folders into the main provision/k8s folderpre-pull-images
andextra-pre-pull-images
text filepre-pull-images
needs to get updated whenever the manifests inside either the k8s version folder or the manifests inside the gocli change - add a call toupdate-pre-pull-images.sh
to check idempotency (no changes in repo) incheck-cluster-up.sh
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer: