LAB 3.X Worker node remains in NotReady state

I follow the lab manual step by step, but still the worker remains NotReady. The control plane is prepared and functioning while the worker not. I am currently using Virtualbox for testing, network interfaces are using PROMISCUOUS mode (both set up in network configuration of virtualbox and flag visible when doing ip link).
This is the error showed by the kubelet in the worker node:
E0921 17:06:38.561928 6940 kubelet.go:2855] "Container runtime network not ready" networkReady="NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: cni plugin not initialized"
For some strange reason, when cilium is deployed its configuration file /etc/cni/net.d/05-cilium.conflist is only present on the control plane, while on the worker node, the directory /etc/cni/net.d/ is empty. If I manually create such file on the worker node then it
becomes ready, but then other errors arise.
This is what comes up when the worker is ready (after manually adding the cni configuration), the pods for cilium on the worker are not ready and showing CrashLoopBackOff.
E0921 17:12:14.231789 9444 pod_workers.go:1300] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"cilium-operator\" with CrashLoopBackOff: \"back-off 10s restarting failed container=cilium-operator pod=cilium-operator-788c4f69bc-7vwg6_kube-system(d5a3dbed-4191-481a-8d66-07e542e9cc6c)\"" pod="kube-system/cilium-operator-788c4f69bc-7vwg6" podUID="d5a3dbed-4191-481a-8d66-07e542e9cc6c"
I have literally followed every single millimeter of the lab manuals, I really don't know what is wrong.
Comments
-
Hi @mariano.dangelo,
How many network interfaces on each VM? Is promiscuous set to "allow all"? What type of network is selected (bridged, nat, etc.)? What are the IP addresses of the VMs? What is the CPU count, memory and disk size of each VM? What is the guest OS on the VMs?
Regards,
-Chris0 -
Hello @chrispokorni,
each vm has 2 network interfaces, one NAT and the other one is host-only. Promiscuous is indeed set to "allow all". The network as I said is a NAT network. IP addresses of VMs are static, 172.23.19.0/24 network, with IPs being 172.23.19.30 and 172.23.19.40. Each VM has 4 CPUs and 8GB of RAM, with a disk size of 25GB. The guest OS on the VMs is Ubuntu 20.04. I am sure that the control-plane's alias/domain name is correct, I can see it f0 -
Hi @mariano.dangelo,
For a successful cluster bootstrapping on VirtualBox please use a single bridged adapter on each VM, with promiscuous mode enabled to "allow all".
Regards,
-Chris0 -
hello @chrispokorni,
Thank you, I'll try. I think this should be also included in the lab manual, as there is nothing regarding bridged adapters, but just NAT networks. Should I disable my host-only adapter as well? How could that harm my cluster?
0
Categories
- All Categories
- 51 LFX Mentorship
- 104 LFX Mentorship: Linux Kernel
- 576 Linux Foundation IT Professional Programs
- 304 Cloud Engineer IT Professional Program
- 125 Advanced Cloud Engineer IT Professional Program
- 53 DevOps Engineer IT Professional Program
- 61 Cloud Native Developer IT Professional Program
- 5 Express Training Courses
- 5 Express Courses - Discussion Forum
- 2K Training Courses
- 19 LFC110 Class Forum
- 7 LFC131 Class Forum
- 27 LFD102 Class Forum
- 157 LFD103 Class Forum
- 20 LFD121 Class Forum
- 1 LFD137 Class Forum
- 61 LFD201 Class Forum
- 1 LFD210 Class Forum
- LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 611 LFD259 Class Forum
- 105 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFD273 Class Forum
- 2 LFS145 Class Forum
- 24 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 11 LFS203 Class Forum
- 75 LFS207 Class Forum
- 300 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 11 LFS244 Class Forum
- 36 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 140 LFS253 Class Forum
- LFS254 Class Forum
- 1.1K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 93 LFS260 Class Forum
- 132 LFS261 Class Forum
- 33 LFS262 Class Forum
- 80 LFS263 Class Forum
- 15 LFS264 Class Forum
- 11 LFS266 Class Forum
- 18 LFS267 Class Forum
- 17 LFS268 Class Forum
- 23 LFS269 Class Forum
- 203 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- LFS281 Class Forum
- 235 LFW211 Class Forum
- 172 LFW212 Class Forum
- 7 SKF100 Class Forum
- SKF200 Class Forum
- 903 Hardware
- 219 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 Multimedia
- 209 Networking
- 101 Printers & Scanners
- 85 Storage
- 763 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 142 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 479 Linux System Administration
- 41 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 78 Network Management
- 108 System Management
- 49 Web Management
- 68 Mobile Computing
- 23 Android
- 30 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 537 Off Topic
- 131 Introductions
- 217 Small Talk
- 21 Study Material
- 826 Programming and Development
- 278 Kernel Development
- 514 Software Development
- 928 Software
- 260 Applications
- 184 Command Line
- 3 Compiling/Installing
- 76 Games
- 316 Installation
- 61 All In Program
- 61 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)