Revert cri-o freeze

[akalenyu]

What this PR does / why we need it:
Once the cri-o issues are fixed, we should continue consuming latest cri-o.

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:

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

NONE

[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 assign brianmcarey for approval. 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

[akalenyu]

/hold

/cc @enp0s3 @brianmcarey
@haircommander @giuseppe do you happen to know whether https://issues.redhat.com/browse/OCPBUGS-45394 is fixed in 1.31.3?

[brianmcarey]

/retest

[haircommander]

so the fix should be in crun, so any cri-o version should work given the correct crun version (1.19)

[akalenyu]

so the fix should be in crun, so any cri-o version should work given the correct crun version (1.19)

@brianmcarey I believe we're consuming crun through the cri-o install? and that does not have 1.19 yet

[haircommander]

ah gotcha. 1.31.1 does not have an updated crun. I am trying to figure out a bug I've introduced and once I do that i'll cut a 1.31.2 which will have new crun

[enp0s3]

@haircommander Hi, if for example we want to consume latest CRIO with latest crun, is there DNF repo that contains nightly RPMs of latest CRIO and crun builds?

[enp0s3]

@ormergi Hi, do you know if there was a progress since CRIO was pinned? AFAIK it were the network tests that failed to create the network tap device.
We would benefit from investing time researching this issue and remove the CRI-O pinning, since we've missed important breaking change that caused disk hotplug to break, it was revealed first in D/S, while it shouldn't.

[enp0s3]

@ormergi Sorry I've missed that @akalenyu pointed out https://issues.redhat.com/browse/OCPBUGS-45394
It looks like it should fix the network tests

[brianmcarey]

/retest

[akalenyu]

ah gotcha. 1.31.1 does not have an updated crun. I am trying to figure out a bug I've introduced and once I do that i'll cut a 1.31.2 which will have new crun

I believe you meant 1.31.4? I am looking at latest dnf install -y cri-o which is 1.31.3 and that has crun 1.18.2
which I believe does not have

cgroup, systemd: do not override devices on update. If the "update" request has no device block configured, do not reset the previously configuration.

(only in crun 1.19 according to release notes)

# /usr/libexec/crio/crun --version
crun version 1.18.2

[kubevirt-bot]

@akalenyu: The following tests 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-up-kind-sriov	94883af	link	false	/test check-up-kind-sriov
check-provision-k8s-1.32	94883af	link	true	/test check-provision-k8s-1.32
check-provision-k8s-1.30	94883af	link	true	/test check-provision-k8s-1.30
check-provision-k8s-1.31-s390x	94883af	link	true	/test check-provision-k8s-1.31-s390x
check-provision-k8s-1.31	94883af	link	true	/test check-provision-k8s-1.31

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.