Kubernetes Recipe VM failed to start - Raise Network Interfaces
-
Ive Attempted to create a kubernetes cluster using the recipe several times now on several different versions of Xen Orchestra (most recently on the just released latest, 5.108), but have never managed to get any particular configuration of settings to load. The first VM initialized always gets stuck, and at what appears to be quite an early step.
The VM will load and show grub, and start up, but then hang at the cloud-init log line. (apperently attempting to raise network interfaces)
When I initialized the cluster from the settings, I did not pick specific IP addresses as I use DHCP to centralize control of IP addresses.
Ive tried to SSH into the machine to determine what is wrong from logs, but have been unable to connect. I am unsure what to do from here to debug this situation.
Assistance is appreciated. Thanks.
-
Pinging the @Team-DevOps
-
Hi @deefdragon ,
Can you share the settings you used in the form?
According to the logs you have an issue with the network: can you check that the dhcp is working well (attributed IP address, netmask, gateway, etc. you can see in the console/screenshot) ?
Maybe you can try to reboot the VM, and try to connect again in ssh. If it works, you can extract the cloud-init logs from
/var/log/cloud-init-output.log.Cyrille
-
Hihi @Cyrille
Confirmed the IP is getting set in DHCP as expected in my router & the data all looks correct as to what I would expect it to be.
I am able to ping the address, but ssh still just connection-refused's me.
Rebooting the VM to attempt to force it is resulting in the same ssh result.
For some details that might help, pool-wide eth5 is the network that all my other VMs are on, and is the only one actively connected to the network. 0-4 are all unplugged. The listed NFS storage is a networked storage, not an on-machine storage (hosted on truenas, thus its name)
I tried using a different network real quick just to see, and got the same results as previously (tho with no DHCP assigned as the network is not connected to my DHCP server) with getting stuck at 4 seconds before spewing out that table at 400~ with the network info.
-
@deefdragon Can you try with static IPs?
Does your network have Internet access? The recipe needs it to update Debian and install microk8s. -
@Cyrille The network does have the ability to reach out to the internet to update&install.
Ive attempted to do an install with Manually entering some IPs. That does appear to be getting it to go further along the initialization process.
The control plane atleast was able to reach a point where it could show me the login prompt, and the worker appears to be installing now.
-
Hey @deefdragon did the installation finished using static IP addresses?
-
@nathanael-h yeah, the installation finished, tho as mentioned above I would prefer to assign my ips via dhcp, so it's not perfect.
(mind, I'm currently using a manually deployed cluster just fine, so I'm in no rush to really figure out why the automatic ups are failing)
Unrelated, are there plans to eventually allow for up/down scaling the recipe later? With the CCM, setting up vm auto scaling should be possible if the recipe supports it right?
