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

Tuned devices_udev_regex=^INTERFACE=(?!!usb0) double exclamation mark

XMLWordPrintable

    • +
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the reduction of the network queue did not work as expected for inverted rules such as `!ens0`. This happened because the exclamation mark symbol was duplicated in the generated tuned profile. With this release, the duplication no longer occurs so that inverted rules apply as intended. (link:https://issues.redhat.com/browse/OCPBUGS-33929[*OCPBUGS-33929*]).
      Show
      * Previously, the reduction of the network queue did not work as expected for inverted rules such as `!ens0`. This happened because the exclamation mark symbol was duplicated in the generated tuned profile. With this release, the duplication no longer occurs so that inverted rules apply as intended. (link: https://issues.redhat.com/browse/OCPBUGS-33929 [* OCPBUGS-33929 *]).
    • Bug Fix
    • Done
    • Hide
      2024-04-17: Addressing review comments. Should be ready for merge.
      2024-04-10: PR posted, waiting for CI
      Show
      2024-04-17: Addressing review comments. Should be ready for merge. 2024-04-10: PR posted, waiting for CI

      This is a clone of issue OCPBUGS-30111. The following is the description of the original issue:
      —

      What were you trying to do that didn't work?

      Trying to apply the following PAO configuration [^master-profile-pao.yaml]

      Please provide the package NVR for which bug is seen:

      How reproducible:

      100%

      Steps to reproduce

      1. Apply the provided PAO CR [^master-profile-pao.yaml]
      2. Check the tuned status 
      3.  

      Expected results

      [labadmin@TestSrv testautomation]$ oc get profile -A
NAMESPACE                                NAME                                     TUNED                                       APPLIED   DEGRADED   AGE
openshift-cluster-node-tuning-operator   master0   openshift-node-performance-master-profile   True      False      3m21s
openshift-cluster-node-tuning-operator   master1   openshift-node-performance-master-profile   True      False      5d21h
openshift-cluster-node-tuning-operator   master2   openshift-node-performance-master-profile   True      False      5d22h
openshift-cluster-node-tuning-operator   worker0   openshift-node-performance-worker-profile   True      False      5d22h
openshift-cluster-node-tuning-operator   worker1   openshift-node-performance-worker-profile   True      False      5d22h
openshift-cluster-node-tuning-operator   worker2   openshift-node-performance-worker-profile   True      False      5d22h

      Actual results

      [labadmin@TestSrv pao]$ oc get tuned -n openshift-cluster-node-tuning-operator openshift-node-performance-master-profile -o yaml

      [^openshift-node-performance-master-profile.yaml]

      [net]
type=net
devices_udev_regex=^INTERFACE=(?!!usb0)
channels=combined 10
nf_conntrack_hashsize=131072

              msivak@redhat.com Martin Sivak
              openshift-crt-jira-prow OpenShift Prow Bot
              Mallapadi Niranjan Mallapadi Niranjan
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: