-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
Link etcd certificates for calico-node error #3464
Comments
@forkballpitch Could you provide the information listed in the issue template (OS, distrib,.., command-line) and the task name that raises the error? |
@mirwan i just cloned this source "https://github.com/kubernetes-incubator/kubespray.git" os : ubuntu 16.04.4 |
I'm having the same problem. Ubuntu 16.04 clean installs on both kubespray host and kube nodes, kubespray pulled from git, command line:
|
First can you confirm that:
If so, could you check if there was any failed task before (on etcd servers during cert generation, memory checks...) ? |
For me:
Other possibly related errors or warnings are:
but also in the same task:
I didn't find any failed tasks. Does this help? |
Additional notes:
I'm completely new to ansible and trying kubespray for the first time, so I'd love to help out but I'm still figuring out how it works. |
First, I think you must used |
i have a somethin dont understand. first ini file is error file and second one has no error ansible-playbook -b -v -i inventory/prod/hosts.ini cluster.yml host.ini ( error in node4) [k8s-cluster:children] [all] [kube-master] [kube-node] [etcd] [calico-rr] host.ini (no error, i remove node1~3 in node part) [k8s-cluster:children] [all] [kube-master] [kube-node] node4 [etcd] [calico-rr] and it works~! |
@forkballpitch I didn't think a server could in kube-node and in etcd/kube-master at the same time. The doc says it can, I will inquire. |
Actually, mixing masters/etcd and workload (i.e. nodes) is not a best practice in production. |
@forkballpitch Btw have you reset your servers (with reset.yml playbook) between your deployments with the 2 inventories? |
I've played around with Ansible and kubespray and opened #3486 as that is what fixed it for me. |
I have reproduced this issue with ansible==2.7.0 |
@bartlaarhoven Regarding @dkozlov 's comment, what version of ansible are you using? |
@mirwa, I'm having the same problem and I could confirm Kubespray revision 3b750ca returns this error when using Ansible 2.7.0. It works with Ansible 2.6.3 as dkozlov said. |
@dkozlov @mirwan I've used the most recent version of Ansible (fresh install)
|
I was able to reproduce the issue with ansible 2.7. |
I think we currently hit that issue: ansible/ansible#46600 |
I have issues signing the collaboration document (as it should be from my company etc.) but I'd like to point again to my PR #3486 as that fixed it for me in Ansible 2.7 and it uses the same way of distributing certificates as in other parts of kubespray. |
@bartlaarhoven I'm currently testing your branch ;-) |
hey @mirwan any news on this topic? This is a show stopper for me... |
@caruccio There's only one step left before merging the PR#3486 (and I guess you know what's left to be done and certainly why this step cannot be skipped). In the meantime, downgrading to ansible 2.6 could do the trick. |
I see... I live in Brazil and I really known what bureaucracy means for life on earth. |
I'm still facing this problem on v2.7 and master |
@mirwan Do you have a contact point for me at TLF to get me another agreement? |
@thiguetta as said, it's a bug in ansible 2.7, it's not something we can fix in kubespray. |
@bartlaarhoven I don't have any contact point except the one mentioned by the bot (helpdesk@rt.linuxfoundation.org) :-/ |
i've got a error here
help me please.
failed: [node5] (item={u's': u'node-node5.pem', u'd': u'cert.crt'}) => {"changed": false, "item": {"d": "cert.crt", "s": "node-node5.pem"}, "msg": "Error while linking: [Errno 2] No such file or directory", "path": "/etc/calico/certs/cert.crt", "state": "absent"}
and my host.ini file is...
[k8s-cluster:children]
kube-master
kube-node
[all]
node1 ansible_host=209.XXX.188.XX ip=209.XXX.188.XX
node2 ansible_host=209.XXX.188.XXX ip=209.XXX.188.XX
node3 ansible_host=209.XXX.188.XXX ip=209.XXX.188.XX
node4 ansible_host=209.XXX.188.XXX ip=209.XXX.188.XX
node5 ansible_host=209.XXX.188.XXX ip=209.XXX.188.XX
[kube-master]
node1
node2
node3
[kube-node]
node4
node5
[etcd]
node1
node2
node3
[calico-rr]
[vault]
node1
node2
node3
The text was updated successfully, but these errors were encountered: