-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
4.18
-
None
This is a clone of issue OCPBUGS-51191. The following is the description of the original issue:
—
Description of problem:
With a user/cluster CR matching this:
--- apiVersion: tuned.openshift.io/v1 kind: Tuned metadata:  name: configuration-nic  namespace: openshift-cluster-node-tuning-operator spec:  profile:  - data: |    [main]    summary=Configuration to set to 32 the nb of interrupt per NIC    # Make sure the include name matches the PerformanceProfile    include=openshift-node-performance-my-pp-name    [net]    type=net    # Update the NIC name pattern    devices_udev_regex=^INTERFACE=eno(0|1)    channels=combined 16   name: configuration-nic  recommend:  - machineConfigLabels:    machineconfiguration.openshift.io/role: "worker-2"   priority: 19   profile: configuration-nic
I want to use the following template, but it fails to correctly match
Â
--- apiVersion: tuned.openshift.io/v1 kind: Tuned metadata: name: configuration-nic namespace: openshift-cluster-node-tuning-operator spec: profile: {{- range .spec.profile }} - data: | [main] summary=Configuration to set to 32 the nb of interrupt per NIC # Make sure the include name matches the PerformanceProfile include=openshift-node-performance-$name [net] type=net # Update the NIC name pattern    devices_udev_regex=^INTERFACE=(?<ifregex>[^\n\r]+) channels=combined (?<chcount>[0-9]+) name: configuration-nic {{- end }} recommend: - machineConfigLabels: machineconfiguration.openshift.io/role: "worker-2" priority: 19 profile: configuration-nic
Â
Version-Release number of selected component (if applicable):
4.17
How reproducible:
100%
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- clones
-
OCPBUGS-51191 cluster-compare capture group fails with regex content in source CR
-
- Closed
-
- is blocked by
-
OCPBUGS-51191 cluster-compare capture group fails with regex content in source CR
-
- Closed
-
- links to
-
RHBA-2025:3066 OpenShift Container Platform 4.18.z bug fix update