Got stuck on Chapter 3 Installation and Configuration on Node

I got stuck when running the kubeadm and I believe I have followed the step by step instruction. Any feedback would be appriciated.

Operating System: CentOS 7.5
Oracle VM Virtual Box:

• Bridge network, allow all promiscuous mode
• 2 vCPU
• Base memory 4096M
• OS Disk 15G
• DHCP with static IP 192.168.0.31, DNS Server 192.168.0.24

Chapter 3 Installation and Configuration on Node
Steps to reproduce on Node:
1. su - root
2. yum update && yum upgrade –y
3. yum install docker

4. vi /etc/yum.repos.d/kubernetes.repo
   [Kubernetes_Repository]
   name=Kubernetes
   baseurl=https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/
   enabled=1
   gpgcheck=1
   repo_gpgcheck=1
   gpgkey=https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg https://packages.cloud.google.com/yum/doc/yum-key.gpg
5. yum update

6. yum install kubeadm kubelet kubectl –y

7. wget https://docs.projectcalico.org/v3.3/getting-started/kubernetes/installation/hosted/rbac-kdd.yaml
   wget https://docs.projectcalico.org/v3.3/getting-started/kubernetes/installation/hosted/kubernetes-datastore/calico-networking/1.7/calico.yaml

8. less calico.yaml

9. systemctl enable docker.service

10. systemctl enable kubelet.service
11. systemctl stop firewalld
12. swapoff –a
13. kubeadm init --kubernetes-version 1.15.1 --pod-network-cidr 192.168.0.0/16 | tee kubeadm-init.out

Error Result:
[kubelet-check] Initial timeout of 40s passed.
Error execution phase wait-control-plane: couldn’t initialize a Kubernetes cluster
Unfortunately, an error has occurred:
timed out waiting for the condition
This error is likely caused by:

• The kubelet is not running

• The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)
  If you are on a system-powered system, you can try to troubleshoot the error with the following commands :

• ‘systemctl status kubelet’

• ‘journalctl –xeu kubelet’
  Additionally, a control plane component may have crashed or exited when started by the container runtime. To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker .
  Here is one example how you may list all Kubernetes containers running in docker:

• ‘docker ps –a | grep kube | grep –v pause’
  Once you have found the failing container, you can inspect its logs with:

• ‘docker logs CONTAINERID”

When checking kubelet.service, it says “node server031.whiteopen.com” not found but the kubelet is on active(running) state.

When running this command “kubectl –n kube-system get cm kubeadm-config –oyamlkubectl
The result was “The connection to the server localhost:8080 was refused – did you specify the right host or port?”