Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 1487896 Details for
Bug 1626387
[OVN] container cannot access the dns server
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Testing logs
Test-log.txt (text/plain), 8.42 KB, created by
Weibin Liang
on 2018-09-27 19:38:48 UTC
(
hide
)
Description:
Testing logs
Filename:
MIME Type:
Creator:
Weibin Liang
Created:
2018-09-27 19:38:48 UTC
Size:
8.42 KB
patch
obsolete
>## 3.10 SDN setup >[root@ip-172-18-14-111 ec2-user]# cat /etc/resolv.conf ># nameserver updated by /etc/NetworkManager/dispatcher.d/99-origin-dns.sh ># Generated by NetworkManager >search cluster.local ec2.internal >nameserver 172.18.14.111 >[root@ip-172-18-14-111 ec2-user]# systemctl status dnsmasq >\u25cf dnsmasq.service - DNS caching server. > Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled) > Drop-In: /etc/systemd/system/dnsmasq.service.d > \u2514\u2500override.conf > Active: active (running) since Thu 2018-09-27 14:01:28 EDT; 52min ago > Main PID: 5978 (dnsmasq) > CGroup: /system.slice/dnsmasq.service > \u2514\u25005978 /usr/sbin/dnsmasq -k > >Sep 27 14:52:44 ip-172-18-14-111.ec2.internal dnsmasq[5978]: using nameserver 127.0.0.1#53 for domain in-addr.arpa >Sep 27 14:52:44 ip-172-18-14-111.ec2.internal dnsmasq[5978]: using nameserver 127.0.0.1#53 for domain cluster.local >Sep 27 14:53:14 ip-172-18-14-111.ec2.internal dnsmasq[5978]: setting upstream servers from DBus >Sep 27 14:53:14 ip-172-18-14-111.ec2.internal dnsmasq[5978]: using nameserver 172.18.0.2#53 >Sep 27 14:53:14 ip-172-18-14-111.ec2.internal dnsmasq[5978]: using nameserver 127.0.0.1#53 for domain in-addr.arpa >Sep 27 14:53:14 ip-172-18-14-111.ec2.internal dnsmasq[5978]: using nameserver 127.0.0.1#53 for domain cluster.local >Sep 27 14:53:44 ip-172-18-14-111.ec2.internal dnsmasq[5978]: setting upstream servers from DBus >Sep 27 14:53:44 ip-172-18-14-111.ec2.internal dnsmasq[5978]: using nameserver 172.18.0.2#53 >Sep 27 14:53:44 ip-172-18-14-111.ec2.internal dnsmasq[5978]: using nameserver 127.0.0.1#53 for domain in-addr.arpa >Sep 27 14:53:44 ip-172-18-14-111.ec2.internal dnsmasq[5978]: using nameserver 127.0.0.1#53 for domain cluster.local >[root@ip-172-18-14-111 ec2-user]# >[root@ip-172-18-14-111 ec2-user]# oc create -f https://raw.githubusercontent.com/weliang1/Openshift_Networking/master/OSE3.3/blue-pod1.json >route.route.openshift.io/blue-route created >service/blue-service created >pod/blue-pod-1 created >[root@ip-172-18-14-111 ec2-user]# oc get all >NAME READY STATUS RESTARTS AGE >pod/blue-pod-1 1/1 Running 0 22s > >NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE >service/blue-service ClusterIP 172.30.202.50 <none> 8080/TCP 22s > >NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD >route.route.openshift.io/blue-route blue.example.com blue-service <all> None > >[root@ip-172-18-14-111 ec2-user]# nslookup 172.30.202.50 172.30.0.1 >Server: 172.30.0.1 >Address: 172.30.0.1#53 > >Non-authoritative answer: >50.202.30.172.in-addr.arpa name = blue-service.p1.svc.cluster.local. > >Authoritative answers can be found from: > >[root@ip-172-18-14-111 ec2-user]# nslookup blue-service.p1.svc.cluster.local. 172.30.0.1 >Server: 172.30.0.1 >Address: 172.30.0.1#53 > >Name: blue-service.p1.svc.cluster.local >Address: 172.30.202.50 > >[root@ip-172-18-14-111 ec2-user]# oc rsh blue-pod-1 >/ # nslookup 172.30.202.50 172.30.0.1 >Server: 172.30.0.1 >Address 1: 172.30.0.1 kubernetes.default.svc.cluster.local > >Name: 172.30.202.50 >Address 1: 172.30.202.50 blue-service.p1.svc.cluster.local >/ # nslookup blue-service.p1.svc.cluster.local. 172.30.0.1 >Server: 172.30.0.1 >Address 1: 172.30.0.1 kubernetes.default.svc.cluster.local > >Name: blue-service.p1.svc.cluster.local. >Address 1: 172.30.202.50 blue-service.p1.svc.cluster.local >/ # cat /etc/resolv.conf >nameserver 172.18.14.114 >search p1.svc.cluster.local svc.cluster.local cluster.local ec2.internal >options ndots:5 >/ # >/ # ping yahoo.com >PING yahoo.com (98.138.219.232) 56(84) bytes of data. >64 bytes from media-router-fp2.prod1.media.vip.ne1.yahoo.com (98.138.219.232): icmp_seq=1 ttl=43 time=32.9 ms >64 bytes from media-router-fp2.prod1.media.vip.ne1.yahoo.com (98.138.219.232): icmp_seq=2 ttl=43 time=32.7 ms >64 bytes from media-router-fp2.prod1.media.vip.ne1.yahoo.com (98.138.219.232): icmp_seq=3 ttl=43 time=32.8 ms > >/ # nslookup yahoo.com >nslookup: can't resolve '(null)': Name does not resolve > >Name: yahoo.com >Address 1: 98.138.219.232 media-router-fp2.prod1.media.vip.ne1.yahoo.com >Address 2: 72.30.35.9 media-router-fp1.prod1.media.vip.bf1.yahoo.com >Address 3: 72.30.35.10 media-router-fp2.prod1.media.vip.bf1.yahoo.com >Address 4: 98.137.246.7 media-router-fp1.prod1.media.vip.gq1.yahoo.com >Address 5: 98.137.246.8 media-router-fp2.prod1.media.vip.gq1.yahoo.com >Address 6: 98.138.219.231 media-router-fp1.prod1.media.vip.ne1.yahoo.com >Address 7: 2001:4998:58:1836::10 media-router-fp1.prod1.media.vip.bf1.yahoo.com >Address 8: 2001:4998:58:1836::11 media-router-fp2.prod1.media.vip.bf1.yahoo.com >Address 9: 2001:4998:c:1023::4 media-router-fp1.prod1.media.vip.gq1.yahoo.com >Address 10: 2001:4998:c:1023::5 media-router-fp2.prod1.media.vip.gq1.yahoo.com >Address 11: 2001:4998:44:41d::3 media-router-fp1.prod1.media.vip.ne1.yahoo.com >Address 12: 2001:4998:44:41d::4 media-router-fp2.prod1.media.vip.ne1.yahoo.com >/ # > > > > > > > > > >## 3.10 OVN setup: >[root@ip-172-18-10-62 ec2-user]# cat /etc/resolv.conf ># nameserver updated by /etc/NetworkManager/dispatcher.d/99-origin-dns.sh ># Generated by NetworkManager >search cluster.local ec2.internal >nameserver 172.18.10.62 >[root@ip-172-18-10-62 ec2-user]# systemctl status dnsmasq >\u25cf dnsmasq.service - DNS caching server. > Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled) > Drop-In: /etc/systemd/system/dnsmasq.service.d > \u2514\u2500override.conf > Active: active (running) since Thu 2018-09-27 09:22:45 EDT; 5h 30min ago > Main PID: 5949 (dnsmasq) > CGroup: /system.slice/dnsmasq.service > \u2514\u25005949 /usr/sbin/dnsmasq -k > >Sep 27 09:22:45 ip-172-18-10-62.ec2.internal systemd[1]: Started DNS caching server.. >Sep 27 09:22:45 ip-172-18-10-62.ec2.internal systemd[1]: Starting DNS caching server.... >Sep 27 09:22:45 ip-172-18-10-62.ec2.internal dnsmasq[5949]: started, version 2.76 cachesize 10000 >Sep 27 09:22:45 ip-172-18-10-62.ec2.internal dnsmasq[5949]: compile time options: IPv6 GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop...ct inotify >Sep 27 09:22:45 ip-172-18-10-62.ec2.internal dnsmasq[5949]: DBus support enabled: connected to system bus >Sep 27 09:22:45 ip-172-18-10-62.ec2.internal dnsmasq[5949]: using nameserver 172.18.0.2#53 >Sep 27 09:22:45 ip-172-18-10-62.ec2.internal dnsmasq[5949]: read /etc/hosts - 2 addresses >Hint: Some lines were ellipsized, use -l to show in full. >[root@ip-172-18-10-62 ec2-user]# >[root@ip-172-18-10-62 ec2-user]# oc create -f https://raw.githubusercontent.com/weliang1/Openshift_Networking/master/OSE3.3/blue-pod1.json >route.route.openshift.io/blue-route created >service/blue-service created >pod/blue-pod-1 created >[root@ip-172-18-10-62 ec2-user]# oc get all >NAME READY STATUS RESTARTS AGE >pod/blue-pod-1 1/1 Running 0 7m > >NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE >service/blue-service ClusterIP 172.30.84.227 <none> 8080/TCP 7m > >NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD >route.route.openshift.io/blue-route blue.example.com blue-service <all> None >[root@ip-172-18-10-62 ec2-user]# nslookup 172.30.84.227 172.30.0.1 >Server: 172.30.0.1 >Address: 172.30.0.1#53 > >Non-authoritative answer: >227.84.30.172.in-addr.arpa name = blue-service.p1.svc.cluster.local. > >Authoritative answers can be found from: > >[root@ip-172-18-10-62 ec2-user]# nslookup blue-service.p1.svc.cluster.local. 172.30.0.1 >Server: 172.30.0.1 >Address: 172.30.0.1#53 > >Name: blue-service.p1.svc.cluster.local >Address: 172.30.84.227 > >[root@ip-172-18-10-62 ec2-user]# oc rsh blue-pod-1 >/ # nslookup 172.30.84.227 172.30.0.1 >Server: 172.30.0.1 >Address 1: 172.30.0.1 > >Name: 172.30.84.227 >Address 1: 172.30.84.227 >/ # nslookup blue-service.p1.svc.cluster.local. 172.30.0.1 >Server: 172.30.0.1 >Address 1: 172.30.0.1 > >nslookup: can't resolve 'blue-service.p1.svc.cluster.local.': Try again >/ # >/ # cat /etc/resolv.conf >nameserver 172.18.14.129 >search p1.svc.cluster.local svc.cluster.local cluster.local ec2.internal >options ndots:5 >/ # >[root@ip-172-18-10-62 ec2-user]# oc rsh blue-pod-1 >/ # ping yahoo.com >ping: unknown host yahoo.com >/ # >/ # nslookup yahoo.com >nslookup: can't resolve '(null)': Name does not resolve > >nslookup: can't resolve 'yahoo.com': Try again >/ #
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1626387
: 1487896 |
1494514