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

An invalid isolated partition cgroups error when cpu load-balance disabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • None
    • 4.16
    • Node / CRI-O
    • Important
    • No
    • Approved
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress
    • 5/3: This might be directly related to the mixed cpu feature recently added (dev preview) currently its not reproduced in other flows. When capacity allows - provide additional info for RHEL.

      Description of problem:

      On 4.16 with Centos stream Cores 4.16(having RHEL9.4) when trying to deploy a pod with "cpu-load-balancing.crio.io": "disable" crio annotation, the cpuset.cpus.partition under the container cgroups is:
      isolated invalid (Parent is not a partition root)
      
      This is probably because the remote isolated partition feature patches are missing from the Centos stream (on RHEL 9.2 everything works)

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

      4.16 with Centos stream Cores (RHEL9.4)
      
      uname -r
      5.14.0-408.el9.x86_64
      

      How reproducible:

          Always

      Steps to Reproduce:

      1. Apply performance profile
      2.Apply guaranteed pod with integral number of cpus and "cpu-load-balancing.crio.io": "disable" crio annotation annotation.     
      3. exec the pod and check the cpuset.cpus.partition      

      Actual results:

          The cpuset.cpus.partition has isolated invalid (Parent is not a partition root) value

      Expected results:

          The  cpuset.cpus.partition should be Isolated (no invalid)

      Additional info:

      On RHEL 9.2 everything works

              titzhak Talor Itzhak
              titzhak Talor Itzhak
              Sunil Choudhary Sunil Choudhary
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: