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

tuned: tuned breaks dynamic IRQ affinity

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • 4.15
    • Performance Addon Operator
    • None
    • +
    • Important
    • No
    • False
    • Hide

      None

      Show
      None

      This is a clone of issue OCPBUGS-30306. The following is the description of the original issue:
      —
      This is a clone of issue OCPBUGS-26400. The following is the description of the original issue:
      —
      Description of problem:

      If GloballyDisableIrqLoadBalancing in disabled in the performance profile then irqs should be balanced across all cpus minus the cpus that are explicitly removed by crio via the pod annotation irq-load-balancing.crio.io: "disable"

There's an issue when the scheduler plugin in tuned will attempt to affine all irqs to the non-isolated cores. Isolated here means non-reserved, not truly isolated cores. This is directly at odds with the user intent. So now we have tuned fighting with crio/irqbalance both trying to do different things. 

Scenarios
- If a pod get’s launched with the annotation after tuned has started, runtime or after a reboot - ok 
- On a reboot if tuned recovers after the guaranteed pod has been launched - broken
- If tuned restarts at runtime for any reason - broken

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

         4.14 and likely earlier

      How reproducible:

          See description

      Steps to Reproduce:

          1.See description 
    2.
    3.

      Actual results:

      Expected results:

      Additional info:

       

            [OCPBUGS-31844] tuned: tuned breaks dynamic IRQ affinity

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Important: OpenShift Container Platform 4.14.22 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2024:1891

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Important: OpenShift Container Platform 4.14.22 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:1891

            Priya Parasuram added a comment -

            The errata for the 4.14.22 release is not cut. However, the latest nightly has the PR included, which I am expecting to be in the official build for 4.14.22. 

            Info from the latest nightly:

            CLUSTER-NODE-TUNING-OPERATOR

            • Scheduler plugin: ignore IRQs (#1023) #1023  (link to the PR)

            Hope this helps. I'm also trying to verify if it is possible to get an early info on the official build.

             

            Priya Parasuram added a comment - The errata for the 4.14.22 release is not cut. However, the latest nightly has the PR included, which I am expecting to be in the official build for 4.14.22.  Info from the latest nightly: CLUSTER-NODE-TUNING-OPERATOR Scheduler plugin: ignore IRQs (#1023)  #1023   (link to the PR) Hope this helps. I'm also trying to verify if it is possible to get an early info on the official build.  

            Priya Parasuram added a comment -

            rhn-support-dmoessner : checking if it is included in 4.14.22. 

            cc: yquinn@redhat.com rh-ee-sizucchi 

            Priya Parasuram added a comment - rhn-support-dmoessner : checking if it is included in 4.14.22.  cc: yquinn@redhat.com rh-ee-sizucchi  

            Mallapadi Niranjan added a comment -

            rh-ee-sizucchi  we are waiting for the OCP nightly release to pull the fixed NTO image. will verify as soon as we have the updated nightly image 

            Mallapadi Niranjan added a comment - rh-ee-sizucchi   we are waiting for the OCP nightly release to pull the fixed NTO image. will verify as soon as we have the updated nightly image 

            OpenShift Jira Bot added a comment -

            Hi yquinn@redhat.com,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi yquinn@redhat.com , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

              yquinn@redhat.com Yanir Quinn
              openshift-crt-jira-prow OpenShift Prow Bot
              Mallapadi Niranjan Mallapadi Niranjan
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: