-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.17
-
None
-
None
-
False
-
Description of problem:
In this doc: https://docs.openshift.com/container-platform/4.17/scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.html, "Disabling Transparent Huge Pages" and "Configuring huge pages at boot time" works fine but "Consuming huge pages resources using the Downward API" section requires some change in the instructions to verify as the pod goes to pending state due to Insufficient hugepages-1Gi
Version-Release number of selected component (if applicable):
4.17
How reproducible:
100%
Steps to Reproduce:
1. Create 4.17 Openshift cluster and login into it. 2. Follow the instructions given under "Consuming huge pages resources using the Downward API" section of https://docs.openshift.com/container-platform/4.17/scalability_and_performance/what-huge-pages-do-and-how-they-are-consumed-by-apps.html
Actual results:
When you create hugepages-volume pod it will be in Pending state due to the error message which says "0/6 nodes are available: 3 Insufficient hugepages-1Gi, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/6 nodes are available: 3 No preemption victims found for incoming pod, 3 Preemption is not helpful for scheduling."
Expected results:
Pod should be in Running state.
Additional info: