-
Bug
-
Resolution: Done-Errata
-
Major
-
4.8, 4.14, 4.15, 4.16, 4.17, 4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
No
-
None
-
None
-
None
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-57328. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-57327. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-7747. The following is the description of the original issue:
—
Description of problem:
`autoSizingReserved: true` feature reserves too low CPU allocation even less than default
Version-Release number of selected component (if applicable):
OCP 4.8+
How reproducible:
Always
Steps to Reproduce:
1. enable `autoSizingReserved: true` feature in KubeletConfig 2. check CPU reservation on nodes /etc/node-sizing.env after KubeletConfig applied https://docs.openshift.com/container-platform/4.10/nodes/nodes/nodes-nodes-resources-configuring.html#nodes-nodes-resources-configuring-auto_nodes-nodes-resources-configuring
Actual results:
Example 4xCPU + 16GB node = SYSTEM_RESERVED_CPU=0.08
Expected results:
`autoSizingReserved` should not reserve lesser CPU than would be reserved by default without any KubeletConfig in place. Allocations calculated by `autoSizingReserved` feature should add to the base CPU reservation of 500m
Additional info:
In OpenShift Container Platform 4.10, half of a CPU core (500 millicore) is now reserved by the system by default compared to OpenShift Container Platform 3.11 and previous versions. The sizes are determined taking that into consideration. https://docs.openshift.com/container-platform/4.10/scalability_and_performance/recommended-host-practices.html#master-node-sizing_recommended-host-practices
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- links to
-
RHBA-2025:11359
OpenShift Container Platform 4.17.36 bug fix update