The product_uuid and the hostname should be unique across nodes #31
From @vganapathy1 on October 26, 2016 6:50
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Kubernetes version (use
weve-cube installation failed with the Peer name collision,
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
On master node:
Installed wave-cube as below,
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
CUrling kube-apiserver from a node:
nslookup on both master & node
Anything else do we need to know:
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:
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 :
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 !
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: