Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
kubeadm join failing preflight checks #347
Is this a BUG REPORT or FEATURE REQUEST?
What you expected to happen?
Normal completion of
How to reproduce it (as minimally and precisely as possible)?
Try to perform
Anything else we need to know?
Skipping preflight checks allows the join to run normally.
I suspect the problem is this line:
It was not updated to match the changes to
Seeing this on 1.7.1. Even after providing node-name, it still complains with the same error. Workaround is to skip pre-flight checks. Looks like, the error is happening in this validation:
Actually looks to be here:
Looks like the HostNameCheck for node join missed an update in kubernetes/kubernetes@e20f5a3
This was referenced
Jul 18, 2017
referenced this issue
Jul 19, 2017
Edit Edit: I wasn't completely wrong, the purported fix was backported but the issue is still in 1.7.2.
Apologies for all the back and forth and confusion here. I did more digging and I do see the purported fix backported to v1.7.2: https://github.com/kubernetes/kubernetes/blob/v1.7.2/cmd/kubeadm/app/preflight/checks.go#L544
I also confirmed that 1.7.2 still has the problem. I think that means kubernetes/kubernetes#49073 is not a complete fix for the problem.
As far as I can tell, the problem is that in v1.7.0, the hostname check had the following structure:
In v1.7.2, the structure of this check changed. The hostnameCheck struct now has a
Based on this, I think the correct fix is probably to populate
Does anyone see a problem with this analysis? This is easy enough to fix, and also to add an additional test around to verify that we're not passing blank strings as the node name.
Just to add an additional issue when using the --config flag and setting