Description of problem: In the PolicyGenTemplate we're defining a PerformanceProfile with the parameter "globallyDisableIrqLoadBalancing" set to false. When the template gets rendered we can see that it has no "globallyDisableIrqLoadBalancing" set and as such when it gets created, it gets configured with the default value which is "true". On top of that we can see that the apiVersion used is "apiVersion: performance.openshift.io/v1" and it should be "apiVersion: performance.openshift.io/v2". The template being used: - fileName: PerformanceProfile.yaml policyName: "perfprofile-policy" metadata: name: performance-sno annotations: kubeletconfig.experimental: | {"topologyManagerScope": "pod", "systemReserved": {"memory": "9Gi"} } spec: additionalKernelArgs: - "idle=poll" - "rcupdate.rcu_normal_after_boot=0" - "nohz_full=2-15,18-19,22-23,26-31" cpu: isolated: "2-15,18-19,22-23,26-31" reserved: "0-1,16-17,20-21,24-25" globallyDisableIrqLoadBalancing: false hugepages: defaultHugepagesSize: 1G pages: - size: 1G count: 4 numa: topologyPolicy: single-numa-node realTimeKernel: enabled: true net: userLevelNetworking: true Version-Release number of selected component (if applicable): 4.8 How reproducible: Always Steps to Reproduce: 1. Create a performanceprofile template with the parameter set to false 2. Check that it gets loaded in the cluster with the default value of true 3. Actual results: PerformanceProfile object gets rendered without the globallyDisableIrqLoadBalancing parameter. Expected results: PerformanceProfile object gets rendered with the globallyDisableIrqLoadBalancing parameter. Additional info:
Verified using cnf-features-deploy master branch. Before and after override on my cluster: [kni@provisionhost-0-0 ~]$ oc get performanceprofiles.performance.openshift.io -o yaml | grep Irq globallyDisableIrqLoadBalancing: true [kni@provisionhost-0-0 ~]$ oc get performanceprofiles.performance.openshift.io -o yaml | grep Irq globallyDisableIrqLoadBalancing: false
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 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-2022:0056