You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux m4c45 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
What happened?
Sometimes if you receive big size response from dns, you can get this errors:
If you have search domain in /etc/resolv.conf, and if it can be resolved (eg. wildcard *.mydomain.tld in dns):
# kubeadm init
[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.
unable to get URL "https://storage.googleapis.com/kubernetes-release/release/stable-1.7.txt": Get https://storage.googleapis.com/kubernetes-release/release/stable-1.7.txt: x509: certificate has expired or is not yet valid
If you have no resolvable search domain in /etc/resolv.conf:
# kubeadm init
[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.
unable to get URL "https://storage.googleapis.com/kubernetes-release/release/stable-1.7.txt": Get https://storage.googleapis.com/kubernetes-release/release/stable-1.7.txt: dial tcp: lookup storage.googleapis.com on 10.36.1.10:53: read udp 10.36.128.180:40844->10.36.1.10:53: i/o timeout
What you expected to happen?
That Installation will be continued.
How to reproduce it (as minimally and precisely as possible)?
@kvaps Because this relates to a potential bug in go's internal DNS resolver, I'm not sure what kubeadm can do here. I don't think it's sensible for us to continually retry runtime errors from the language. IMO it's a fatal error that needs to be resolved externally (i.e. by flushing your DNS server). What do you think?
I think this issue more for information than for doing something here.
If someone has same problem than me, he can find this issue.
So I'll close it, thank you.
BUG REPORT
Versions
kubeadm version:
Environment:
uname -a
):What happened?
Sometimes if you receive big size response from dns, you can get this errors:
If you have search domain in /etc/resolv.conf, and if it can be resolved (eg. wildcard *.mydomain.tld in dns):
If you have no resolvable search domain in /etc/resolv.conf:
What you expected to happen?
That Installation will be continued.
How to reproduce it (as minimally and precisely as possible)?
Please read golang/go#21160
Anything else we need to know?
Conneted: golang/go#21160
The text was updated successfully, but these errors were encountered: