Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error to exec playbook "kubernetes.yml" #39

Open
JaviPG opened this issue Jan 8, 2018 · 6 comments
Open

Error to exec playbook "kubernetes.yml" #39

JaviPG opened this issue Jan 8, 2018 · 6 comments

Comments

@JaviPG
Copy link

JaviPG commented Jan 8, 2018

I trying build the cluster but I have the follow error when I tried launch "ansible-playbook -i hosts kubernetes.yml"

"item": [
"kubelet=1.8.1*",
"kubeadm=1.8.1*",
"kubectl=1.8.1*",
"kubernetes-cni"
],
"msg": [
"'/usr/bin/apt-get -y -o "Dpkg::Options::=--force-confdef" -o "Dpkg::Options::=--force-confold" --force-yes install 'kubelet=1.8.1*' 'kubeadm=1.8.1*' 'kubectl=1.8.1*' 'kubernetes-cni'' failed: E: Unable to correct problems, you have held broken packages.",
""
],
"rc": "100",
"stderr": [
"E: Unable to correct problems, you have held broken packages.",
""
],
"stderr_lines": [
"E: Unable to correct problems, you have held broken packages."
],
"stdout": [
"Reading package lists...",
"Building dependency tree...",
"Reading state information...",
"Some packages could not be installed. This may mean that you have",
"requested an impossible situation or if you are using the unstable",
"distribution that some required packages have not yet been created",
"or been moved out of Incoming.",
"The following information may help to resolve the situation:",
"",
"The following packages have unmet dependencies:",
" kubelet : Depends: kubernetes-cni (= 0.5.1) but 0.6.0-00 is to be installed",
""
],

Could you kindly help me please?

@rhuss
Copy link
Collaborator

rhuss commented Jan 10, 2018

I have to check this later. Seems that there have been some package updates lately. 'hope to resolve this until the weekend.

@JaviPG
Copy link
Author

JaviPG commented Jan 10, 2018

First of all thank you for your interest in helping me.

At the end, I could run the cluster. I changed kubernetes version 1.8.1 to 1.9.1 in the follow file:
roles / kubernetes / defaults / main.yml

@rhuss, thanks for your contribution. This project is very interestant and powerfull. I'll try colaborate with you.

@patrickschlaepfer
Copy link

Changed the version in the file you mentioned. Not really a impact. Seems that there is kind of mix-n-match of versions of kubernetes/docker. Has anyone a running cluster out there. with a actual version. Or which versions do work together?
As soon there is an apt-get upgrade, seems it gets destroyed.

@m1m1s1ku
Copy link

m1m1s1ku commented Feb 7, 2018

This project is pure magic ! :')

kubernetesVersion: "latest-1.8" needs to be changed to : kubernetesVersion: "latest-1.9"

in roles/kubernetes/templates/kubeadm.yml

(and also thanks to JaviPG, I could run the cluster. I also changed kubernetes version 1.8.1 to 1.9.2
in roles/kubernetes/defaults/main.yml)

@rhuss
Copy link
Collaborator

rhuss commented Feb 8, 2018

@Ghostfly thanks for the heads up ! I'm still behind in my backlog, so I won't be able to update playbooks within the next two weeks. Sorry ...

PRs are always welcome ;-)

@mjudeikis
Copy link
Contributor

mjudeikis commented Feb 25, 2018

#40 update to 1.9 + some other stuff :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants