How Do I Downgrade a cgroup?
Background
The etcd Kubernetes container cannot be started. Run the journalctl -u containerd command to view the containerd log. The following log is displayed:
applying cgroup configuration for process caused \\\"mountpoint for cgroup not found\\\"\"\n
Run the stat -fc %T /sys/fs/cgroup/ command to check the cgroup version. The command output shows that the cgroup version is cgroup2fs. The root cause is that cgroup v2 of Kubernetes has not passed GA and cgroup needs to be downgraded.
Procedure
- Add systemd.unified_cgroup_hierarchy=no to the GRUB_CMDLINE_LINUX configuration item in the /etc/default/grub file and disable cgroup v2.
GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0 systemd.unified_cgroup_hierarchy=no"
- Run the sudo grub-mkconfig -o /boot/grub/grub.cfg command to regenerate the boot.
- Run the reboot command to restart the server.
On-Premises Clusters FAQs
- Why Cannot I Connect an On-Premises Cluster to UCS?
- How Do I Manually Clear Nodes of an On-Premises Cluster?
- How Do I Downgrade a cgroup?
- How Do I Do If VM SSH Connection Times Out?
- How Do I Expand the Storage Disk Capacity of the CIA Add-on in an On-Premises Cluster?
- Why Is the Cluster Console Unavailable After the Master Node Is Shut Down?
- Why Is the Node Not Ready After Scaling-out?
- How Do I Update a CA/TLS Certificate in an On-Premises Cluster?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore