CRI-O service looks for unexpected conmon path
Issue
- CRI-O service looks for
/usr/libexec/crio/conmoneven whenconmon = ""is set in crio.conf. - The crio service fails to start on OpenShift nodes with following error messages:
Sep 23 12:05:37 master01.example.com crio[2267]: time="2021-09-23 12:05:37.541190556Z" level=info msg="Using default capabilities: CAP_CHOWN, CAP_DAC_OVERRIDE, CAP_FSETID, CAP_FOWNER, CAP_NET_RAW, CAP_SETGID, CAP_SETUID, CAP_SETPCAP, CAP_NET_BIND_SERVICE, CAP_SYS_CHROOT, CAP_KILL"
Sep 23 12:05:37 master01.example.com crio[2267]: time="2021-09-23 12:05:37.589350381Z" level=fatal msg="Validating runtime config: conmon validation: invalid conmon path: stat /usr/libexec/crio/conmon: no such file or directory"
Environment
- Red Hat OpenShift Container Platform [RHOCP]
- 4.7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.