is dhcp must for the switches used in kubernetes install environment?

10 views

Skip to first unread message

Oğuz Yarımtepe

unread,

Aug 13, 2017, 12:29:57 PM8/13/17

to coreo...@googlegroups.com

Hi,

I am trying to install Kubernetes at my Baremetal nodes. The nodes have CoreOS installed and i have installed master node from https://github.com/coreos/coreos-kubernetes/blob/master/multi-node/generic/controller-install.sh without errors. When i try adding the worker node i got the below error:

Aug 11 09:20:43 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:43.875024 1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:43 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:43.875060 1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:44 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:44.913283 1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:44 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:44.913337 1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:45 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:45.958095 1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:45 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:45.958131 1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:47 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:47.002463 1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:47 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:47.002490 1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:48 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:48.046091 1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

Aug 11 09:20:48 worker1-k8s.host.foo.net flannel-wrapper[1270]: E0811 09:20:48.046119 1270 network.go:102] failed to register network: failed to acquire lease: out of subnets

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: locksmithd.service: Service hold-off time over, scheduling restart.

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: Stopped Cluster reboot manager.

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: Started Cluster reboot manager.

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: Reboot strategy "best-effort" is deprecated and will be removed in the future.

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: Please explicitly set the reboot strategy to one of [off reboot etcd-lock]

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: See https://coreos.com/os/docs/latest/update-strategies.html for details on configuring reboot strategies.

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: No configured reboot window

Aug 11 09:20:48 worker1-k8s.host.foo.net locksmithd[1567]: Cannot get update engine status: The name com.coreos.update1 was not provided by any .service files

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: locksmithd.service: Main process exited, code=exited, status=1/FAILURE

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: locksmithd.service: Unit entered failed state.

Aug 11 09:20:48 worker1-k8s.host.foo.net systemd[1]: locksmithd.service: Failed with result 'exit-code'.

Aug 11 09:20:49 worker1-k8s.host.foo.net flannel-wrapper[1270]: I0811 09:20:49.091620 1270 local_manager.go:179] Picking subnet in range 172.16.101.128 ... 172.16.101.128

I have dummy switches but no dhcp enabled? Can it a be the reason of the error? Any idea? Or any other non problamatic methos to install Kubernetes on Baremetal? The script has only 1.5.4 support it seems. I need to install the lates version also.