-
Bug
-
Resolution: Done-Errata
-
Undefined
-
None
-
4.18.z, 4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-49823. The following is the description of the original issue:
—
Description of problem:
Applying a performance profile with unsupported hugepages size, (In this example 512) fails to create the performanceprofile and it becomes degraded.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Label one of the worker nodes with worker-cnf
2. Create an mcp for worker-cnf
3. Apply this performanceprofile
apiVersion: performance.openshift.io/v2
kind: PerformanceProfile
metadata:
name: performance
spec:
cpu:
isolated: 1-3,4-6
reserved: 0,7
hugepages:
defaultHugepagesSize: 512M
pages:
- count: 1
node: 0
size: 512M
- count: 128
node: 1
size: 2M
machineConfigPoolSelector:
machineconfiguration.openshift.io/role: worker-cnf
net:
userLevelNetworking: true
nodeSelector:
node-role.kubernetes.io/worker-cnf: ''
kernelPageSize: 64k
numa:
topologyPolicy: single-numa-node
realTimeKernel:
enabled: false
workloadHints:
highPowerConsumption: true
perPodPowerManagement: false
realTime: true
Actual results:
Expected results:
Additional info:
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2025:2705
OpenShift Container Platform 4.18.z bug fix update