Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nodes in not ready state with RHEL/CentOS systems #104

Closed
galal-hussein opened this issue Dec 5, 2017 · 1 comment
Closed

Nodes in not ready state with RHEL/CentOS systems #104

galal-hussein opened this issue Dec 5, 2017 · 1 comment
Assignees
Labels

Comments

@galal-hussein
Copy link
Contributor

rke v0.0.7-dev

rke failed when deploying network/addon jobs because node were in not ready state, when describing nodes i found this error message:

kubectl describe nodes
Name:               node-01
Roles:              etcd,master,worker
..........
KubeletNotReady              Failed to start ContainerManager mkdir /sys/fs/cgroup/cpuacct,cpu: read-only file system,runtime network not ready

Adding "/sys/fs/cgroup:/sys/fs/cgroup:rw" to kubelet volumes solved the problem

@soumyalj
Copy link

soumyalj commented Dec 7, 2017

Reproduced the issue in rke version v0.0.7-dev.
Tested with rke version v0.0.8-dev for RHEL and Centos hosts. Creation of cluster was successful. The nodes were in Ready state. Creation of pods also succeeded.

soumyas-MBP:rke soumya$ kubectl --kubeconfig .kube_config_cluster.yml get nodes
NAME             STATUS    AGE       VERSION
104.236.249.49   Ready     3m        v1.8.3-rancher3
45.55.165.202    Ready     3m        v1.8.3-rancher3

@soumyalj soumyalj closed this as completed Dec 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants