-
Bug
-
Resolution: Done
-
Major
-
None
-
4.14, 4.16, 4.18
This is a clone of issue OCPBUGS-54977. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-54475. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-54312. The following is the description of the original issue:
—
Description of problem:
The current RAN RDS reference files include a fixed list of workloadHints values for the Performance Profile [1] workloadHints: realTime: true highPowerConsumption: false perPodPowerManagement: false This is setting a specific configuration, although we have traditionally considered other options as valid, such as: - Setting "highPowerConsumption: true / perPodPowerManagement: false" to force C0 C-state - Or setting "highPowerConsumption: false / perPodPowerManagement: true" to enable per-pod power management. [1] - https://github.com/openshift-kni/cnf-features-deploy/blob/release-4.18/ztp/kube-compare-reference/required/node-tuning-operator/PerformanceProfile.yaml#L50-L52
Version-Release number of selected component (if applicable):
Seen on RAN RDS versions 4.14 through 4.18
How reproducible:
Always
Steps to Reproduce:
1. Run oc cluster-compare with the RAN RDS as reference against a Performance Profile YAML with different workloadHints values
Actual results:
Deviations found
Expected results:
No deviations found
- blocks
-
OCPBUGS-56869 Allow flexibility in workloadHints section of Performance Profile for RAN RDS
-
- Closed
-
- clones
-
OCPBUGS-54977 Allow flexibility in workloadHints section of Performance Profile for RAN RDS
-
- Closed
-
- is blocked by
-
OCPBUGS-54977 Allow flexibility in workloadHints section of Performance Profile for RAN RDS
-
- Closed
-
- is cloned by
-
OCPBUGS-56869 Allow flexibility in workloadHints section of Performance Profile for RAN RDS
-
- Closed
-
- links to
- mentioned on