Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Rishi Misra
Thanks. I will follow up with all the suggestions with my admin. On Thu, Mar 23, 2017 at 3:18 PM, Clayton Coleman wrote: > Unfortunately openshift needs iptables running to provide the connectivity > between services - if your administrator has a restrictive firewall in >

Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Clayton Coleman
Unfortunately openshift needs iptables running to provide the connectivity between services - if your administrator has a restrictive firewall in place on your machine via iptables you may need an exception in the iptables rules to let that functionality run. On Mar 23, 2017, at 2:31 PM, Rishi

Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Cesar Wong
Your container network needs to have access to the master API and DNS ports. Instructions to allow that are in step #3 here: https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#linux > On Mar

Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Clayton Coleman
One more test (sorry) - inside a debug container, can you $ curl -k https://172.30.0.1 It should return a list of json responses. If it can't, it either means: MASTER_IP is not being correctly registered into your endpoints ("oc get endpoints -n default" should include master ip) or a firewall

Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Rishi Misra
<> *Yes. * root@vote-1-7acnx-debug:/app# ping MASTER_IP PING MASTER_IP: 56 data bytes 64 bytes from MASTER_IP: icmp_seq=0 ttl=64 time=0.077 ms <> *Yes.* /===/ # dig @MASTER_IP -p 8053 google.com ; <<>> DiG 9.9.4-RedHat-9.9.4-38.el7_3.2 <<>> @MASTER_IP -p 8053

Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Rishi Misra
Here are the results: // # oc get pods NAME READY STATUSRESTARTS AGE vote-1-7acnx 1/1 Running 0 38s # oc debug pod/vote-1-7acnx Debugging with pod/vote-1-7acnx-debug, original command: gunicorn app:app -b 0.0.0.0:80

Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Clayton Coleman
Ok, can you create a running container (oc debug pod/NAME_OF_POD) and inside of it run the same dig commands (you'll need a docker image with dig already installed) On Thu, Mar 23, 2017 at 12:46 PM, Rishi Misra wrote: > It seems to: > >

Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Rishi Misra
It seems to: /=/ # dig @MASTER_IP -p 53 kubernetes.default.svc.cluster.local ; <<>> DiG 9.9.4-RedHat-9.9.4-38.el7_3.2 <<>> @MASTER_IP -p 53 kubernetes.default.svc.cluster.local ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode:

Re: Question on DNS when running Master/Node on same node

2017-03-23 Thread Clayton Coleman
Can you run: $ dig @MASTER_IP -p 53 kubernetes.default.svc.cluster.local from the host and verify it works? And if so, then try $ dig @MASTER_IP -p 53 www.google.com On Thu, Mar 23, 2017 at 12:35 PM, Rishi Misra wrote: > Hi there, > > I am having difficulty

Question on DNS when running Master/Node on same node

2017-03-23 Thread Rishi Misra
Hi there, I am having difficulty getting DNS to work on OpenShift 1.4. When I start all-in-one server now I get following two messages which I presume are generated for master and node running on same server: /==/ openshift start > /tmp/openshift.log 2>&1