On 01/20/2017 11:13 PM, Josh Berkus wrote: > On 01/20/2017 10:55 AM, Dusty Mabe wrote: >> Please test it out so that we can get the new kernel karma'd as soon as >> possible: >> >> ostree remote add --set=gpg-verify=false kerneltest >> https://dustymabe.fedorapeople.org/repo/ >> rpm-ostree rebase kerneltest:fedora-atomic/25/x86_64/docker-host > > OK, running this I get a failure at certificate configuration: > > TASK [kubernetes : Run create cert script on master] > *************************** > fatal: [172.31.36.80]: FAILED! => {"changed": true, "cmd": > ["/usr/local/libexec/kubernetes/make-ca-cert.sh"], "delta": > "0:00:20.840371", "end": "2017-01-21 04:02:00.774712", "failed": true, > "rc": 6, "start": "2017-01-21 04:01:39.934341", "stderr": "curl: (6) > Could not resolve host: storage.googleapis.com", "stdout": "", > "stdout_lines": [], "warnings": []} > > And indeed, when I log into each instance, it's unable to resolve > storage.googleapis.com, or for that matter anything else. > > -bash-4.3# ping www.yahoo.com > ping: www.yahoo.com: Name or service not known > > I'll check on a "clean" system which doesn't have a halfway completed > kubernetes-ansible deploy on it. But for now, my verdict is that DNS is > still broken.
This sounds like dns on your node is broken, which is different than the issue we were seeing before (which was a connection issue between containers running on the same node). Can you check your /etc/resolv.conf to make sure it has good information in it? _______________________________________________ cloud mailing list -- [email protected] To unsubscribe send an email to [email protected]
