Using crio and kubernetes CI job fails on fedora 32

[alicefr]

The kubernetes tests with cri-o on fedora 32 are failing
cc @fabiano

kata_ci_job.log

[alicefr]

My guess is that the clean-up has not been correctly done. Just not sure what.

[fidencio]

Device "cni0" does not exist.
Start crio service
Waiting for cri socket /var/run/crio/crio.sock (try 1)
Waiting for cri socket /var/run/crio/crio.sock (try 2)
Waiting for cri socket /var/run/crio/crio.sock (try 3)
Waiting for cri socket /var/run/crio/crio.sock (try 4)
Waiting for cri socket /var/run/crio/crio.sock (try 5)
● crio.service - CRI-O daemon
     Loaded: loaded (/etc/systemd/system/crio.service; disabled; vendor preset: disabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2021-02-17 07:18:42 EST; 3s ago
       Docs: https://github.com/cri-o/cri-o
    Process: 46374 ExecStart=/usr/local/bin/crio --log-level debug (code=exited, status=1/FAILURE)
   Main PID: 46374 (code=exited, status=1/FAILURE)

Feb 17 07:18:42 kata-fedora-32 systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE
Feb 17 07:18:42 kata-fedora-32 systemd[1]: crio.service: Failed with result 'exit-code'.
Failed at 95: sudo systemctl status "${cri_runtime}" --no-pager
Failed at 79: ./init.sh

CRI-O didn't even start. Leave this one for me and I'll take a look soon-ish.

[fidencio]

@alicefr, can you assign this one to me? :-)

[alicefr]

fyi I tried also on a fresh installed and got a failure on the same error