Changes to the community structure and the menu bar
Significant changes have happened to the structure of our community and our drop down menu bar. READ ABOUT IT HERE
SMAX User Discussions
cancel

SMA-X on AWS - Impossible to start services juste after CDF installation

Highlighted
etravella  Valued Contributor..
 Valued Contributor..

SMA-X on AWS - Impossible to start services juste after CDF installation

Hi,

Juste after installation of the CDF, It's impossible for me to launch again services. When I use kube-start.sh to start services, "kubelet" service never starts (timeout).

[root@ip-21-0-1-10 bin]# ./kube-start.sh 

Starting service docker-bootstrap ................ Started

Starting service docker .......................... Started

Starting service kubelet ......................... Timeout

[root@ip-21-0-1-10 bin]#

Here is the log of the "kubelet" service (by entering this command --> "systemctl status kubelet -l") :

juin 14 07:07:37 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:37.051206   14542 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://21.0.1.100:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-21-0-1-10.eu-west-1.compute.internal&resourceVersion=0: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:37 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:37.051227   14542 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:413: Failed to list *v1.Service: Get https://21.0.1.100:8443/api/v1/services?resourceVersion=0: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:40 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:40.059002   14542 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://21.0.1.100:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-21-0-1-10.eu-west-1.compute.internal&resourceVersion=0: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:40 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:40.059103   14542 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:422: Failed to list *v1.Node: Get https://21.0.1.100:8443/api/v1/nodes?fieldSelector=metadata.name%3Dip-21-0-1-10.eu-west-1.compute.internal&resourceVersion=0: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:40 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:40.059180   14542 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:413: Failed to list *v1.Service: Get https://21.0.1.100:8443/api/v1/services?resourceVersion=0: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:43 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:43.064957   14542 kubelet_node_status.go:107] Unable to register node "ip-21-0-1-10.eu-west-1.compute.internal" with API server: Post https://21.0.1.100:8443/api/v1/nodes: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:43 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:43.064977   14542 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/config/apiserver.go:47: Failed to list *v1.Pod: Get https://21.0.1.100:8443/api/v1/pods?fieldSelector=spec.nodeName%3Dip-21-0-1-10.eu-west-1.compute.internal&resourceVersion=0: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:43 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:43.065054   14542 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:422: Failed to list *v1.Node: Get https://21.0.1.100:8443/api/v1/nodes?fieldSelector=metadata.name%3Dip-21-0-1-10.eu-west-1.compute.internal&resourceVersion=0: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:43 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:43.065054   14542 reflector.go:205] k8s.io/kubernetes/pkg/kubelet/kubelet.go:413: Failed to list *v1.Service: Get https://21.0.1.100:8443/api/v1/services?resourceVersion=0: dial tcp 21.0.1.100:8443: getsockopt: no route to host

juin 14 07:07:43 ip-21-0-1-10.eu-west-1.compute.internal kubelet[14542]: E0614 07:07:43.231765   14542 eviction_manager.go:238] eviction manager: unexpected err: failed to get node info: node 'ip-21-0-1-10.eu-west-1.compute.internal' not found

In this log :

ip-21-0-1-10.eu-west-1.compute.internal is the private DNS of my first Master Node,

21.0.1.100 is the load balancer IP (secondary IP addresse of my first Master Node like described here : https://docs.microfocus.com/itom/Service_Management_Automation_-_X:2018.02/Install_19895362/assign-private-IP-as-VIP-master-1).

Is anyone could help me to solve this problem ?

In advance thank you.

Best regards,

Eric

 

2 REPLIES

Re: SMA-X on AWS - Impossible to start services juste after CDF installation

Cornel Spinu
Frequent Visitor..

Re: SMA-X on AWS - Impossible to start services juste after CDF installation

Hi,

There is not enough information in here, could you please clarify:

  • can you confirm this is a 2018.02 install
  • do you have a multi-master configuration - if yes, are you just at the initial step of installing CDF on the first master or have you actually installed CDF on all 3 masters already
  • why did you need to run kube-start.sh (it is not part of the install procedure). Did you manually do a kube-stop.sh before this and on which node(s)?

There are many reasons why your VIP address might not be reachable e.g. security groups configuration issue or the VIP has switched to a different master node (in case you have 3 masters up already) due to kube-stop/kube-start. We can troubleshhot more once I better understand the context.

Regards,

Cornel