> > is your machine (the centos7 vm) running dnsmasq or anything else on port > 53? If so, shut it down prior to bringing up your cluster. > > Nothing is running on 53: tcp 0 0 localhost:10443 0.0.0.0:* LISTEN
tcp 0 0 localhost:10444 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:http 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:senomix02 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN tcp 0 0 localhost:smtp 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:https 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:pcsync-https 0.0.0.0:* LISTEN tcp6 0 0 [::]:jetcmeserver [::]:* LISTEN tcp6 0 0 [::]:ssh [::]:* LISTEN tcp6 0 0 [::]:afs3-callback [::]:* LISTEN tcp6 0 0 localhost:smtp [::]:* LISTEN tcp6 0 0 [::]:newoak [::]:* LISTEN tcp6 0 0 [::]:10250 [::]:* LISTEN udp 0 0 0.0.0.0:64109 0.0.0.0:* udp 0 0 0.0.0.0:20230 0.0.0.0:* udp 0 0 0.0.0.0:senomix02 0.0.0.0:* udp 0 0 0.0.0.0:bootpc 0.0.0.0:* udp 0 0 0.0.0.0:bootpc 0.0.0.0:* udp 0 0 localhost:323 0.0.0.0:* udp6 0 0 [::]:64109 [::]:* udp6 0 0 [::]:15385 [::]:* udp6 0 0 localhost:323 [::]:* raw6 0 0 [::]:ipv6-icmp [::]:* 7 raw6 0 0 [::]:ipv6-icmp [::]:* Firewalld is running...should I add an open up 53? > what the master container can resolve is not relevant, but if you want to > diagnose things further, start a different pod (like the jenkins pod) and > rsh into that pod and see > 1) whether it can resolve hosts > 2) what its /etc/resolv.conf value is > 3) whether it has external connectivity (independent of its ability to > resolve hostnames) > I did fire up another container and it can't resolve service DNS names
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
