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

Workload partitioning wrong CRI-O configuration key

XMLWordPrintable

    • Important
    • 1
    • T&PS 2022 #12
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Customer Escalated

      Description of problem:

      Workload partitioning wrong CRI-O configuration key. The doc said that CRI-O workload partition configuration keys are `cpushares` and `CPUs` but it looks like the `CPUs` is incorrect and the correct key is `cpuset`.
      https://docs.openshift.com/container-platform/4.11/scalability_and_performance/sno-du-enabling-workload-partitioning-on-single-node-openshift.html#sno-du-enabling-workload-partitioning_sno-du-enabling-workload-partitioning-on-single-node-openshift
      https://github.com/cri-o/cri-o/blob/main/docs/crio.conf.5.md#crioruntimeworkloadresources-table
      
      We need to replace the `CPUs` with `cpuset` as follows:
      
      [crio.runtime.workloads.management]
      activation_annotation = "target.workload.openshift.io/management"
      annotation_prefix = "resources.workload.openshift.io"
      [crio.runtime.workloads.management.resources]
      cpushares = 0
      cpuset = "0-1, 52-53" 

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

      4.11.5

      How reproducible:

      Always

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

      Workload partitioning cannot be configured correctly

      Expected results:

      Workload partitioning configured correctly

      Additional info:

       

       

            rhn-support-rohennes Ronan Hennessy
            rhn-support-tkimura Takayoshi Kimura
            Mallapadi Niranjan Mallapadi Niranjan
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: