[Starlingx-discuss] controller-1 failed after unlock

[Yang, Bin]

Hi Bin,
	This file is generated by kubeadm. And kubeadm is executed by puppet. 
	Normally, you should find below log in /var/log/puppet/:
		Executing: 'kubeadm init --config=/etc/kubernetes/kubeadm.yaml'
		...
		/Stage[main]/Platform::Kubernetes::Master::Init/Exec[configure master node]/returns: [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
		...

	If kubeadm does not run properly, you should find some error log.

thanks,
Bin

On Wed, Jul 17, 2019 at 09:11:16AM +0000, Yang, Bin wrote:
>    Dear StarlingX experts,
> 
>     
> 
>    I am exercising installing starlingx (with latest milestone3  image) with
>    virtualbox following the wiki:
>     https://wiki.openstack.org/wiki/StarlingX/Containers/InstallationOnStandard
> 
>     
> 
>    I am able to install/provision controller-0, compute-0, but failed to
>    unlock controller-1, the issue seems to be kubelet.service cannot start
>    due to missing of config file at /var/lib/kubelet/config.yaml :
> 
>     
> 
>    controller-1:~# ls /var/lib/kubelet/ -al
> 
>    total 8
> 
>    drwxr-xr-x.  2 root root 4096 Jun 21 02:27 .
> 
>    drwxr-xr-x. 60 root root 4096 Jul 16 10:43 ..
> 
>     
> 
>     
> 
>    Could anyone who have insight of this issue shed some lights on this issue
>    ?  Thanks in advance
> 
>     
> 
>    Below is the daemon log:
> 
>     
> 
>    2019-07-17T02:06:13.623 controller-1 systemd[1]: info kubelet.service
>    holdoff time over, scheduling restart.
> 
>    2019-07-17T02:06:13.623 controller-1 systemd[1]: warning Cannot add
>    dependency job for unit dev-hugepages.mount, ignoring: Unit is masked.
> 
>    2019-07-17T02:06:13.641 controller-1 systemd[1]: info Stopped Kubernetes
>    Kubelet Server.
> 
>    2019-07-17T02:06:13.647 controller-1 systemd[1]: info Starting Kubernetes
>    Kubelet Server...
> 
>    2019-07-17T02:06:13.000 controller-1 root: info
>    /usr/bin/kubelet-cgroup-setup.sh(481470): Nothing to do, already
>    configured: /sys/fs/cgroup/cpuset/k8s-infra.
> 
>    2019-07-17T02:06:13.664 controller-1 systemd[1]: info Started Kubernetes
>    Kubelet Server.
> 
>    2019-07-17T02:06:13.832 controller-1 kubelet[481475]: info Flag
>    --feature-gates has been deprecated, This parameter should be set via the
>    config file specified by the Kubelet's --config flag. See
>    https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/
>    for more information.
> 
>    2019-07-17T02:06:13.832 controller-1 kubelet[481475]: info Flag
>    --cpu-manager-policy has been deprecated, This parameter should be set via
>    the config file specified by the Kubelet's --config flag. See
>    https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/
>    for more information.
> 
>    2019-07-17T02:06:13.832 controller-1 kubelet[481475]: info F0717
>    02:06:13.831961  481475 server.go:189] failed to load Kubelet config file
>    /var/lib/kubelet/config.yaml, error failed to read kubelet config file
>    "/var/lib/kubelet/config.yaml", error: open /var/lib/kubelet/config.yaml:
>    no such file or directory
> 
>    2019-07-17T02:06:13.837 controller-1 systemd[1]: notice kubelet.service:
>    main process exited, code=exited, status=255/n/a
> 
>    2019-07-17T02:06:13.847 controller-1 systemd[1]: notice Unit
>    kubelet.service entered failed state.
> 
>    2019-07-17T02:06:13.847 controller-1 systemd[1]: warning kubelet.service
>    failed.
> 
>     
> 
>     
> 
>     
> 
>     
> 
>    Best Regards,
> 
>    Bin Yang
> 
>     

> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss