This message was deleted.

When you ran through the installer. Did you see all your network devices? Did you select on that is up? Sounds like it can’t see a network card. Can you verify the port is active on the switch side?

Yes there were two nics on the system, both visible. One up and one down. The latter which was not networked so this was no surprise. The installer won't let you use a downed networked interface anyway (I tried) so I could only choose the only up NIC. Currently that NIC and provided IP address are pingable and reachable on the network - so I don't see any issues there. The management address is the issue, but it seems like the rancherd service won't complete starting up properly anyway.

Can you ssh into the node externally? You can double check the settings in

/oem/harvester.config

ssh works fine. The IP address I put this on doesn't seem to have any problem. It's the management Virtual IP that isn't starting up because rancherd is having issues

good news is that the

ssh

still works for the first node, try to get below information:

sudo -i  
kubectl get pods -A
kubectl get service -A
kubectl get managedchart -A
kubectl get bundle -A
kubectl get bundledeployment -A
ps aux
ip link
ip addr
cat /oem/harvester.config

the install should “just work”. I suspect there is something wrong with the vlanning in the configs that isn’t allowing the kubelet to start.

kubelet does not care vlan

thus check the config….

I think it's something network related. I have another server on the network and harvester install won't even let me configure the network. The error message is vague "Configure network failed: fork/exec /usr/bin/yip: input/output error"

Huzzah