Description of problem:
conmon was moved to run under system.slice as a solution for it getting OOM killed. However, that could possibly lead to it taking away CPU cycles needed by system processes. Alternative solution that use a monitoring routine in CRI-O has been implemented to detect conmon getting OOM Killed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.