What happened?

The crun binary installed by 'crun' role is not used by cri-o at all.

Root cause

The 'crun' role installs the crun binary at /usr/local/bin/crun.

But cri-o does not use it. The 'crun' binary is included in the cri-o tarball and 'cri-o' role installs the crun in /usr/libexec/crio/crun. The crio-o uses this crun binary.

Related PR is #11584

What did you expect to happen?

The cri-o uses /usr/local/bin/crun

I think we have two options to solve this:

1. The cri-o uses /usr/local/bin/crun. The cri-o role does not install 'crun' binary.
2. Use crun binary included in cri-o tarball, and remove 'crun' role, if anyone does not use it.

I'm not sure which one is better. Need discussion.

How can we reproduce it (as minimally and precisely as possible)?

Just enable the cri-o and deploy.

container_manager: crio

OS

Ubuntu 20 (but not depends on it)

Version of Ansible

9.13.0

Version of Python

3.11.0

Version of Kubespray (commit)

2.28.0

Network plugin used

calico

Full inventory with variables

Command used to invoke ansible

Output of ansible run

Anything else we need to know

Related issue: #12233
The crun 1.21 included in cri-o 1.32.4 and 1.33.0 does not work with Ubuntu 20.04.