search

leblancd / kube-v6

Instructions on how to instantiate a multi-node, IPv6-only Kubernetes cluster.
Apache License 2.0
166 stars 22 forks source link

Installation failed while using vagrant #11

Open mmueen opened 5 years ago

mmueen commented 5 years ago

Background: Installation on Windows 10, laptop, HP, core i7, 16 GB memory Virtual box version 6.0.6 Vagrant version 2.2.4 Date: 05/13/2019

Problem: while installing via 'vagrant up' , the installation fails while installing nat vm because of cni version mismatch. The log display is mentioned here. deployment_logs.zip

` k86-nat64: Fetched 110 kB in 1s (87.8 kB/s)

k86-nat64: Reading package lists...

k86-nat64: + echo 'Installing Kubernetes Components...'
k86-nat64: Installing Kubernetes Components...
k86-nat64: + sudo -E apt-get install -qy --allow-downgrades kubelet=1.10.5-00 kubectl=1.10.5-00 kubeadm=1.10.5-00
k86-nat64: Reading package lists...
k86-nat64: Building dependency tree...
k86-nat64: Reading state information...
k86-nat64: Some packages could not be installed. This may mean that you have
k86-nat64: requested an impossible situation or if you are using the unstable
k86-nat64: distribution that some required packages have not yet been created
k86-nat64: or been moved out of Incoming.
k86-nat64: The following information may help to resolve the situation:
k86-nat64: The following packages have unmet dependencies:
k86-nat64:  kubelet : Depends: kubernetes-cni (= 0.6.0) but 0.7.5-00 is to be installed
k86-nat64: E
k86-nat64: :
k86-nat64: Unable to correct problems, you have held broken packages.

The SSH command responded with a non-zero exit status. Vagrant assumes that this means the command failed. The output for this command should be in the log above. Please read the output to determine what went wrong. `

mmueen commented 5 years ago

It was a problem with the Kubernetes version, as this was written a while back and it still uses 1.10.5 K8s version and today 1.14 is out. I specified the K8s version in 'Vagrantfile' to

env['KUBERNETES_VERSION'] = env['KUBERNETES_VERSION'] || "1.14.0"

but after i did cleanup and restarted the ./vagrant-start ... it picked up the 1.10.5 version again, may be from the clone which was downloaded already?

However, I fixed it by changing it in provision_every_node.sh variable directly to

k8s_version="1.14.0"