kubevirtci 1.25 provider

[dhiller]

This is a replacement for the automated PR #866

Todo:

• apply workaround for fetching coredns image issue
• Remove deprecated elements (see deprecation-guide )
  • PodDisruptionBudget (policy/v1beta1 -> policy/v1)
  • PodSecurityPolicy (removed, migrate to Pod Security Admission)
  • ...

/cc @brianmcarey

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from dhiller by writing /assign @dhiller in a comment. For more information see:The Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dhiller]

/test check-provision-k8s-1.25

[kubevirt-bot]

@dhiller: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
check-provision-k8s-1.25	cbe50bd	link	false	/test check-provision-k8s-1.25

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. I understand the commands that are listed here.

[dhiller]

We are currently running into an issue when running provision.sh from 1.25 folder:

+ kubeadm config images pull --kubernetes-version 1.25.0
failed to pull image "registry.k8s.io/kube-apiserver:v1.25.0": output: E0914 09:09:41.663018   39216 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = Unknown desc = invalid policy in \"/etc/containers/policy.json\": Unknown key \"keyPaths\"" image="registry.k8s.io/kube-apiserver:v1.25.0"
time="2022-09-14T09:09:41Z" level=fatal msg="pulling image: rpc error: code = Unknown desc = invalid policy in \"/etc/containers/policy.json\": Unknown key \"keyPaths\""
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher

See cri-o/cri-o#6197

[Barakmor1]

We are currently running into an issue when running provision.sh from 1.25 folder:

+ kubeadm config images pull --kubernetes-version 1.25.0
failed to pull image "registry.k8s.io/kube-apiserver:v1.25.0": output: E0914 09:09:41.663018   39216 remote_image.go:238] "PullImage from image service failed" err="rpc error: code = Unknown desc = invalid policy in \"/etc/containers/policy.json\": Unknown key \"keyPaths\"" image="registry.k8s.io/kube-apiserver:v1.25.0"
time="2022-09-14T09:09:41Z" level=fatal msg="pulling image: rpc error: code = Unknown desc = invalid policy in \"/etc/containers/policy.json\": Unknown key \"keyPaths\""
, error: exit status 1
To see the stack trace of this error execute with --v=5 or higher

See cri-o/cri-o#6197

The strange things is that this error didn't happen in the logs of this PR:
https://storage.googleapis.com/kubevirt-prow/pr-logs/pull/kubevirt_kubevirtci/872/check-provision-k8s-1.25/1565061005749260288/build-log.txt

[Barakmor1]

@dhiller @brianmcarey
The is also a problem with rock-ceph
Currently they are working on some workaround:
rook/rook#10826
I will try to update it to 1.10:
https://github.com/rook/rook/pull/10937/files

[oshoval]

Note that @Barakmor1 also tried to do so, and have problems with macvtap which is part of CNAO

[kubevirt-bot]

@dhiller: PR needs rebase.

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.

[dhiller]

/close

Was merged with #887

[kubevirt-bot]

@dhiller: Closed this PR.

In response to this:

/close

Was merged with #887

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.