Cgroups-per-qos and enforce-node-allocatable options in node-config.yaml are invalid
Issue
- When setting the cgroups-per-qos and enforce-node-allocatable in the node config:
kubeletArguments:
cgroups-per-qos:
- "true"
cgroup-driver:
- "systemd"
enforce-node-allocatable:
- "pods"
It caused the atomic-openshift-node service failure.
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal systemd[1]: Starting Atomic OpenShift Node...
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal atomic-openshift-node[84605]: I0212 18:02:23.694078 84605 start_node.go:250] Reading node configuration from /etc/origin/node/node-config.yaml
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal atomic-openshift-node[84605]: Invalid NodeConfig /etc/origin/node/node-config.yaml
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal atomic-openshift-node[84605]: flag: Invalid value: "cgroups-per-qos": is not a valid flag
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal atomic-openshift-node[84605]: flag: Invalid value: "enforce-node-allocatable": is not a valid flag
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal systemd[1]: atomic-openshift-node.service: main process exited, code=exited, status=255/n/a
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal systemd[1]: Failed to start Atomic OpenShift Node.
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal systemd[1]: Unit atomic-openshift-node.service entered failed state.
Feb 12 18:02:23 ip-10-0-16-62.ap-southeast-2.compute.internal systemd[1]: atomic-openshift-node.service failed.
Environment
- Red Hat Openshift Container Platform
- 3.5.1
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
