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

[enterprise-4.14] Using a performanceprofile is not just not recommended with cgroupv2, it switches the cluster back to v1.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.17.z
    • 4.14.0
    • Documentation / Node
    • None
    • No
    • 3
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      In https://docs.openshift.com/container-platform/4.14/nodes/clusters/nodes-cluster-cgroups-2.html#nodes-clusters-cgroups-2_nodes-cluster-cgroups-2, the documentation mentions:

      Currently, disabling CPU load balancing is not supported by cgroup v2. As a result, you might not get the desired behavior from performance profiles if you have cgroup v2 enabled. Enabling cgroup v2 is not recommended if you are using performance profiles.

      However, if I apply a performanceprofile to my cluster, it automatically switches it back to cgroupv1, and reconciles if I want to change it back to v2.

      It appears the note above is misleading, as it appears not possible to use performanceprofiles with cgroupv2.

      It should be better to warn the user that applying performanceprofiles could automatically set the cluster back to v1 instead of the note above.

      Please confirm with engineering and fix this note.

              rhn-support-stk Subhashini T K
              rhn-support-gveitmic Germano Veit Michel
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: