Hi Naveen; You are right, but I still need guidance.
Cluster is deployed on AWS. [root@ip-10-20-4-38 network-scripts]# cat /etc/resolv.conf search hazelcast-ocp.com nameserver 169.254.169.253 [AWS DNS] And override it and I noticed that origin also add its dispatcher. [root@ip-10-20-4-38 /]# cd ./etc/NetworkManager/dispatcher.d/ [root@ip-10-20-4-38 dispatcher.d]# ls -l total 28 -rwxr-xr-x. 1 root root 175 Sep 12 2016 00-netreport -rwxr-xr-x. 1 root root 100 Aug 18 2016 04-iscsi -rwxr-xr-x. 1 root root 1120 Aug 9 2016 11-dhclient -rwxr-xr-x. 1 root root 442 Jun 23 2015 20-chrony -rwxr-xr-x. 1 root root 52 Apr 17 09:43 99-awsdns [added for AWS DNS, and overrides resolv.conf] -rwxr-xr-x. 1 root root 4000 Apr 17 10:30 99-origin-dns.sh [Origin added after installation] -rwxr-xr-x. 1 root root 719 Dec 23 11:37 cloud-init-azure-hook drwxr-xr-x. 2 root root 6 Mar 29 12:03 no-wait.d drwxr-xr-x. 2 root root 6 Mar 29 12:03 pre-down.d drwxr-xr-x. 2 root root 6 Mar 29 12:03 pre-up.d I needed AWS DNS to resolve host names in order to complete installation successfully for ssh connections, required by ansible playbook. And I am probably missing smh here. I followed installation guide from [https://docs.openshift.com/container-platform/3.5/install_config/install/prerequisites.html <https://docs.openshift.com/container-platform/3.5/install_config/install/prerequisites.html>] VERSION [Container Platform 3.5] [root@ip-10-20-4-38 dispatcher.d]# oc version oc v3.5.5.5 kubernetes v1.5.2+43a9be4 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://master.hazelcast-ocp.com:8443 openshift v3.5.5.5 kubernetes v1.5.2+43a9be4 Kind regards > On 26 Apr 2017, at 14:37, Naveen Kumar Tangallapally > <naveen.tangallapa...@cloudgensys.com> wrote: > > Hi Baris, > > can i let me know the steps for setting up for the DNS. > > because my ods are going in error state. > > Regards... > > > > Regards.... > NAVEEN KUMAR T > Openshift Administrator > Mob:+91 9550220793 > naveen.tangallapa...@cloudgensys.com > <mailto:id%3anaveen.tangallapa...@cloudgensys.com> > > > On Wed, Apr 26, 2017 at 5:02 PM, Barış Aydınöz <ba...@hazelcast.com > <mailto:ba...@hazelcast.com>> wrote: > Problem: > > A Pod in Master can ping to a node in Node, whereas trace path fails. Also, > TCP connection between these pods give timeout errors. > > We have below nodes > > NODES > [root@ip-10-20-4-38 network-scripts]# oc get nodes > NAME STATUS AGE > master.hazelcast-ocp.com <http://master.hazelcast-ocp.com/> Ready 8d > node1.hazelcast-ocp.com <http://node1.hazelcast-ocp.com/> Ready 8d > > Master is also a node > > SUBNET > [root@ip-10-20-4-38 network-scripts]# oc get hostsubnet > NAME HOST HOST IP SUBNET > master.hazelcast-ocp.com <http://master.hazelcast-ocp.com/> > master.hazelcast-ocp.com <http://master.hazelcast-ocp.com/> 54.160.17.51 > 10.128.0.0/23 <http://10.128.0.0/23> > node1.hazelcast-ocp.com <http://node1.hazelcast-ocp.com/> > node1.hazelcast-ocp.com <http://node1.hazelcast-ocp.com/> 52.205.214.205 > 10.129.0.0/23 <http://10.129.0.0/23> > > > PODS > [root@ip-10-20-4-38 network-scripts]# oc get pods > NAME READY STATUS RESTARTS AGE > docker-registry-1-f9lcn 1/1 Running 1 2d > hz-rc-9h10b 1/1 Running 1 15m > hz-rc-fc64l 0/1 Running 0 16m > router-1-pfv0f 1/1 Running 0 3h > > [root@ip-10-20-4-38 network-scripts]# oc describe pod hz-rc-9h10b > Name: hz-rc-9h10b > Namespace: default > Security Policy: restricted > Node: node1.hazelcast-ocp.com/52.205.214.205 > <http://node1.hazelcast-ocp.com/52.205.214.205> > Start Time: Wed, 26 Apr 2017 07:10:28 -0400 > Labels: name=hazelcast-node-hz > Status: Running > IP: 10.129.0.61 > > [root@ip-10-20-4-38 network-scripts]# oc describe pod hz-rc-fc64l > Name: hz-rc-fc64l > Namespace: default > Security Policy: restricted > Node: master.hazelcast-ocp.com/54.160.17.51 > <http://master.hazelcast-ocp.com/54.160.17.51> > Start Time: Wed, 26 Apr 2017 07:09:35 -0400 > Labels: name=hazelcast-node-hz > Status: Running > IP: 10.128.0.100 > > From Master Node: > [root@ip-10-20-4-38 network-scripts]# ip route get 10.129.0.61 > 10.129.0.61 dev tun0 src 10.128.0.1 > cache > > [root@ip-10-20-4-38 network-scripts]# ip a show dev tun0 > 10: tun0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8951 qdisc noqueue state > UNKNOWN qlen 1000 > link/ether e2:b5:07:a5:10:fd brd ff:ff:ff:ff:ff:ff > inet 10.128.0.1/23 <http://10.128.0.1/23> scope global tun0 > valid_lft forever preferred_lft forever > inet6 fe80::e0b5:7ff:fea5:10fd/64 scope link > valid_lft forever preferred_lft forever > > [root@ip-10-20-4-38 network-scripts]# tracepath 10.129.0.61 > 1?: [LOCALHOST] pmtu 8951 > 1: no reply > 2: no reply > 3: no reply > > Could you please advice? > > Thanks in advance > > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com <mailto:users@lists.openshift.redhat.com> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > <http://lists.openshift.redhat.com/openshiftmm/listinfo/users> > >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
