Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-14858

NTO: applying performance profile cause CRI-O to crash

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 4.13.z
    • Performance Addon Operator
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Applying PerformanceProfile causes CRI-O to failed and not start.
According to preliminary investigation,
it seems the 99-runtimes.conf file overwrite the runtime config defined in the 00-default.
This is expected but not clear why it causes CRI-O to failed.

The error:
Jun 09 18:21:20 aarch64-node bash[1173769]: time="2023-06-09 18:21:20.844974396Z" level=fatal msg="validating runtime config: monitor fields translation: failed to translate monitor fields for runtime high-performance: get conmon version: exit status 1"

      Version-Release number of selected component (if applicable):

      Cluster version 4.13.2

      How reproducible:

      Always

      Steps to Reproduce:

      1. Apply PerformanceProfile
2. Check the CRI-O under the node

      Actual results:

      CRIO failed to start

      Expected results:

      CRIO should be healthy and running

      Additional info:

       

              titzhak Talor Itzhak
              titzhak Talor Itzhak
              None
              None
              Gowrishankar Rajaiyan Gowrishankar Rajaiyan
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: