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

[ OCP 4.12] Failed to set SMP affinity of IRQ xxx : No space left on device

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      2024-07-09: Still waiting for kernel, I pinged the engineer again.
      2024-06-19: Waiting for kernel engineering input, this seems to be a driver issue. No known workaround.
      Show
      2024-07-09: Still waiting for kernel, I pinged the engineer again. 2024-06-19: Waiting for kernel engineering input, this seems to be a driver issue. No known workaround.

      Description of problem:

      Application of a tuned profile to reduce IRQ impact on a system with 3 physical NICs, total 16 NIC ports is getting error:
      
      ERROR    tuned.plugins.plugin_scheduler: Failed to set SMP affinity of IRQ 957 to '00000003,00000003': [Errno 28] No space left on device

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

      SNO Openshift 4.12.54

      How reproducible:

      Always

      Steps to Reproduce:

          1. Deploy SNO 
          2. Apply procedure to reduce IRQ:
             https://docs.openshift.com/container-platform/4.12/scalability_and_performance/cnf-low-latency-tuning.html#reducing-nic-queues-using-the-node-tuning-operator_cnf-master
          3. 
          

      Actual results:

      2024-04-05T20:01:19.653726830+00:00 stdout F 2024-04-05 20:01:19,653 ERROR    tuned.plugins.plugin_scheduler: Failed to set SMP affinity of IRQ 957 to '00000003,00000003': [Errno 28] No space left on device
      2024-04-05T20:01:19.653783723+00:00 stdout F 2024-04-05 20:01:19,653 ERROR    tuned.plugins.plugin_scheduler: Failed to set SMP affinity of IRQ 958 to '00000003,00000003': [Errno 28] No space left on device
      2024-04-05T20:01:19.653856624+00:00 stdout F 2024-04-05 20:01:19,653 ERROR    tuned.plugins.plugin_scheduler: Failed to set SMP affinity of IRQ 959 to '00000003,00000003': [Errno 28] No space left on device
      

      Expected results:

      No issue

      Additional info:

      Same procedure on 4.14.17 seems to work as expected

              msivak@redhat.com Martin Sivak
              rhn-support-mabajodu Mario Abajo Duran
              Liquan Cui Liquan Cui
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: