Deb package upgrade from 1.29.1-1.1 to 1.29.2-1.1 moves conmon/crun #7913
Labels
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
What happened?
Updated cri-o package on Ubuntu 22.04 from 1.29.1-1.1 to 1.29.2-1.1 on Kubernetes 1.29 nodes. Nodes subsequently could not create containers (CreateContainerError) as /usr/bin/conmon and /usr/bin/crun had been renamed to /usr/bin/crio-conmon and /usr/bin/crio-crun (looking at past issues it seems like this was done to resolve conflicts in the Red Hat ecosystem?). Rolling back the package appears to have fixed this problem temporarily.
What did you expect to happen?
I did not see anything to indicate that 1.29.1 to 1.29.2 would be a breaking change so I did not expect to see significant impact.
How can we reproduce it (as minimally and precisely as possible)?
Install cri-o=1.29.1-1.1 on Ubuntu 22.04 with Kubernetes 1.29, upgrade to cri-o=1.29.2-1.1, attempt to start containers, should see ContainerCreateError with an event complaining that /usr/bin/conman is not found.
Anything else we need to know?
I'm not sure if I missed something in the upgrade process, or if there's something wrong with the package (e.g. files got moved but cri-o was still looking for them in the wrong place).
CRI-O and Kubernetes version
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)
VMware ESXi
The text was updated successfully, but these errors were encountered: