crio runnner is not properly installed with setup_system.sh for automated installation of Kubernetes

[vladriabtsev]

No description provided.

[fabigr8]

i probably have the same problem.

installed a fresh CL Server on a baremetal today.
followed the installation of Kubernetes based on the CL documentation.

while setup_system.sh the installation fails

-- Console Output:

Disabling swap...
Setting OS Version...
Update started
Version on server (36380) is not newer than system version (36380)
Update complete - System already up-to-date at version 36380
Adding OS Dependencies...
Enabling IP Forwarding...
Setting up modules to load...
Setting up /etc/hosts...
/etc/hosts already configured
Reloading daemons...
Enabling kubelet runner...
Ensuring system is ready...
Detecting and setting up proxy...
Job for crio.service failed because the control process exited with error code.
See "systemctl status crio.service" and "journalctl -xeu crio.service" for details.

-- - journalctl :

May 24 15:36:21 wwin176 systemd[1]: Starting Container Runtime Interface for OCI (CRI-O)...
░░ Subject: A start job for unit crio.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit crio.service has begun execution.
░░
░░ The job identifier is 2520.
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.861172737Z" level=info msg="Starting CRI-O, version: 1.23.2, git: unknown(unknown)"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.861226101Z" level=info msg="Node configuration value for hugetlb cgroup is true"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.861233028Z" level=info msg="Node configuration value for pid cgroup is true"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.861241137Z" level=info msg="Node configuration value for memoryswap cgroup is true"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.861245229Z" level=info msg="Node configuration value for cgroup v2 is false"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.865480180Z" level=info msg="Node configuration value for systemd CollectMode is true"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.869380884Z" level=info msg="Node configuration value for systemd AllowedCPUs is true"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.869482303Z" level=info msg="[graphdriver] using prior storage driver: overlay"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.869743933Z" level=info msg="Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_KILL"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.869794235Z" level=fatal msg="validating runtime config: conmon validation: exec: \"conmon\": executable file not found in $PATH"
May 24 15:36:21 wwin176 systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit crio.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
May 24 15:36:21 wwin176 systemd[1]: crio.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit crio.service has entered the 'failed' state with result 'exit-code'.
May 24 15:36:21 wwin176 systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).
░░ Subject: A start job for unit crio.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit crio.service has finished with a failure.
░░
░░ The job identifier is 2520 and the job result is failed.

---systemctl:

systemctl status crio.service
× crio.service - Container Runtime Interface for OCI (CRI-O)
     Loaded: loaded (/usr/lib/systemd/system/crio.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/crio.service.d
             └─crio-clearlinux.conf
     Active: failed (Result: exit-code) since Tue 2022-05-24 15:36:21 UTC; 15min ago
       Docs: https://github.com/cri-o/cri-o
    Process: 13439 ExecStart=/usr/bin/crio $CRIO_CONFIG_OPTIONS $CRIO_RUNTIME_OPTIONS $CRIO_STORAGE_OPTIONS $CRIO_NETWORK_OPTIONS $CRIO_METRICS_OPTIONS (code=exited, status=1/FAILURE)
   Main PID: 13439 (code=exited, status=1/FAILURE)

May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.861241137Z" level=info msg="Node configuration value for memoryswap cgroup is true"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.861245229Z" level=info msg="Node configuration value for cgroup v2 is false"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.865480180Z" level=info msg="Node configuration value for systemd CollectMode is true"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.869380884Z" level=info msg="Node configuration value for systemd AllowedCPUs is true"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.869482303Z" level=info msg="[graphdriver] using prior storage driver: overlay"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.869743933Z" level=info msg="Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_KILL"
May 24 15:36:21 wwin176 crio[13439]: time="2022-05-24 15:36:21.869794235Z" level=fatal msg="validating runtime config: conmon validation: exec: \"conmon\": executable file not found in $PATH"
May 24 15:36:21 wwin176 systemd[1]: crio.service: Main process exited, code=exited, status=1/FAILURE
May 24 15:36:21 wwin176 systemd[1]: crio.service: Failed with result 'exit-code'.
May 24 15:36:21 wwin176 systemd[1]: Failed to start Container Runtime Interface for OCI (CRI-O).