On 01/20/2017 08:22 PM, Josh Berkus wrote: > On 01/20/2017 08:19 PM, Dusty Mabe wrote: > >> 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? > Never mind, this was the typical issue that the default kube-ansible Flannel IP address range overlaps with default AWS internal IP address ranges. Just one more thing for me to fix with that playbook. DNS test passed, adding karma now. Note that I did get an error testing with Guestbook, pulling the redisslave image. This appears to be unrelated to anything in the recent bugs: Error syncing pod, skipping: failed to "StartContainer" for "slave" with ErrImagePull: "image pull failed for gcr.io/google_samples/gb-redisslave:v1, this may be because there are no credentials on this request. details: (manifest unknown: Failed to fetch \"v1\" from request \"/v2/google_samples/gb-redisslave/manifests/v1\".)" ... most likely, that image doesn't exist anymore. -- -- Josh Berkus Project Atomic Red Hat OSAS _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
