-
Notifications
You must be signed in to change notification settings - Fork 710
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
The product_uuid and the hostname should be unique across nodes #31
Comments
From @luxas on October 26, 2016 16:49 cc @kubernetes/sig-cluster-lifecycle |
From @soualid on November 13, 2016 22:34 Got the following error - that may be related - in
Is there a way to force the renewal of the HWAddr ? Setup informations : kubeadm version
kubectl version
/etc/os-release
uname -a
docker -v
|
From @vganapathy1 on November 15, 2016 15:38 @soualid Surprisingly, the UUID was same for all the VM's I had, which caused the name collision and changing the UUID resolved the issue. To get UUID, I had to get the UUID changed in all the VM's to get this work. If that doesn't work for you, you can check with @errordeveloper and he had a wave-kube patch which also worked for me. |
From @soualid on November 15, 2016 21:7 @vganapathy1 thanks, I confirm that the machine UUID are equals on my machines, the boxes provider (online.net) must use a "clone" install system ("symantec ghost" like) that is not changing this UUID properly between boxes. I will contact them about this issue, but it could be great to be able to workaround this issue by overriding this value at runtime through a Thank you ! |
Is there a solution/workaround for this yet? I read about changing the UUID, how exactly should I do that? |
I ran in the very same issue with a raspi cluster running on Hypriot, all my nodes get the same HW address assigned in Weave:
|
I think all we can do from a kubeadm perspective is document unique product UUIDs as a potential requirement. I imagine there are so many different ways to resolving this per OS, we can't really suggest a specific one. |
Agreed @jamiehannaford, we should just list this as a requirement for everything running smoothly. @jamiehannaford Can you document that please? |
@luxas Sure, I'll get to it next week |
Perfect, thank you! |
This now documented, so we can close 🎉 |
Yayy 🎉 |
added steps for how to verify macaddress and product_uuid with reference to the bug in github that identified this need originally (kubernetes/kubeadm#31)
Hi, @errordeveloper |
From @vganapathy1 on October 26, 2016 6:50
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Kubernetes version (use
kubectl version
):Environment:
VMware vCloud Air VM
7.797 GiB RAM, 2 CPUs each
uname -a
):Kernel Version: 4.4.0-43-generic
What happened:
We used kubeadm and the procedure in Installing Kubernetes on Linux with kubeadm and for the most part the installation went well.
weve-cube installation failed with the Peer name collision,
INFO: 2016/10/26 05:24:32.585405 ->[10.63.33.46:6783] attempting connection INFO: 2016/10/26 05:24:32.587778 ->[10.63.33.46:6783|72:47:96:69:16:bb(Ubuntu14041-mars09)]: connection shutting down due to error: local "72:47:96:69:16:bb(Ubuntu14041-mars09)" and remote "72:47:96:69:16:bb(Ubuntu14041-mars08)" peer names collision
What you expected to happen:
weve-cube installation should have successful and brought the kube-dns up!
How to reproduce it (as minimally and precisely as possible):
On master node:
kubeadm init --api-advertise-addresses=$IP
On Node:
kubeadm join --token $actualtoken $IP
Installed wave-cube as below,
`# kubectl apply -f https://git.io/weave-kube
daemonset "weave-net" created`
kube-dns didn't not start as expected,
Both master and node gets assigned with the same HWaddr causing name collision
` on Master
docker logs a65253346635
INFO: 2016/10/26 05:24:20.719919 Command line options: map[ipalloc-range:10.32.0.0/12 nickname:Ubuntu14041-mars08 no-dns:true docker-api: http-addr:127.0.0.1:6784 ipalloc-init:consensus=2 datapath:datapath name:72:47:96:69:16:bb port:6783]
INFO: 2016/10/26 05:24:20.730839 Communication between peers is unencrypted.
INFO: 2016/10/26 05:24:20.971010 Our name is 72:47:96:69:16:bb(Ubuntu14041-mars08)
On Node,
docker logs a65253346635
INFO: 2016/10/26 05:23:39.312294 Command line options: map[datapath:datapath ipalloc-range:10.32.0.0/12 name:72:47:96:69:16:bb port:6783 docker-api: http-addr:127.0.0.1:6784 ipalloc-init:consensus=2 nickname:Ubuntu14041-mars09 no-dns:true]
INFO: 2016/10/26 05:23:39.314095 Communication between peers is unencrypted.
INFO: 2016/10/26 05:23:39.323302 Our name is 72:47:96:69:16:bb(Ubuntu14041-mars09)
`
CUrling kube-apiserver from a node:
root@Ubuntu14041-mars09:~# curl -k https://10.0.0.1 Unauthorized
nslookup on both master & node
root@Ubuntu14041-mars08:/# curl -k https://10.0.0.1 Unauthorized root@Ubuntu14041-mars08:/# nslookup kubernetes.default Server: 10.30.48.37 Address: 10.30.48.37#53 ** server can't find kubernetes.default: NXDOMAIN
Anything else do we need to know:
iptables -S
kube-proxy-amd logs had the following entries,
Copied from original issue: kubernetes/kubernetes#35591
The text was updated successfully, but these errors were encountered: