Bug 1491850
| Summary: | DNS resolution is broken when installing on host with multiple NICs | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anton Sherkhonov <asherkho> |
| Component: | Installer | Assignee: | Michael Gugino <mgugino> |
| Status: | CLOSED ERRATA | QA Contact: | Gan Huang <ghuang> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.6.0 | CC: | aos-bugs, asherkho, jialiu, jokerman, mmccomas, pportant |
| Target Milestone: | --- | Keywords: | NeedsTestCase |
| Target Release: | 3.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-11-28 22:10:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Anton Sherkhonov
2017-09-14 20:19:33 UTC
Anton, Which IP address is in /etc/resolv.conf? I imagine not the value of openshift_ip but instead the default interface? I'm working on a refactor of the dispatcher script that instead of listening on a specific address it listens to all interfaces other than lo. I imagine that would address the issue. Scott, yes. /etc/resolv.conf has one `nameserver <ip>` entry, where the <ip> is the ip of the default interface of the node. `openshift_ip` for that node is defined by inventory, it's the ip of the 2nd NIC. https://github.com/openshift/openshift-ansible/pull/5778 should fix this in 3.7 https://github.com/openshift/openshift-ansible/pull/5891 was merged to address this https://github.com/openshift/openshift-ansible/pull/5953 probably necessary also to avoid racing at startup In 3.7.0-0.189.0 Verified in openshift-ansible-3.7.0-0.190.0.git.0.129e91a.el7.noarch.rpm
1) ##Spin up instances with two NICs:
# ip addr |grep eth |grep inet
inet 172.16.120.98/24 brd 172.16.120.255 scope global dynamic eth0
inet 192.168.33.3/24 brd 192.168.33.255 scope global dynamic eth1
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 172.16.120.1 0.0.0.0 UG 100 0 0 eth0
10.128.0.0 0.0.0.0 255.252.0.0 U 0 0 0 tun0
169.254.169.254 192.168.33.1 255.255.255.255 UGH 100 0 0 eth1
172.16.120.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0
172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0
172.30.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0
192.168.33.0 0.0.0.0 255.255.255.0 U 100 0 0 eth1
2) ##Trigger installation against two NICs of the instances:
# cat inventory_hosts
<--snip-->
[masters]
host-8-240-252.host.centralci.eng.rdu2.redhat.com
[nodes]
host-8-240-252.host.centralci.eng.rdu2.redhat.com openshift_node_labels="{'role': 'node'}" openshift_ip=192.168.33.3 openshift_dns_ip=192.168.33.3
host-8-241-27.host.centralci.eng.rdu2.redhat.com openshift_node_labels="{'role': 'node','registry': 'enabled','router': 'enabled'}" openshift_ip=192.168.33.5 openshift_dns_ip=192.168.33.5
[etcd]
host-8-241-126.host.centralci.eng.rdu2.redhat.com
[nfs]
host-8-240-252.host.centralci.eng.rdu2.redhat.com
<--snip-->
3) ##Check the configurations
# cat /etc/resolv.conf
# nameserver updated by /etc/NetworkManager/dispatcher.d/99-origin-dns.sh
# Generated by NetworkManager
search openstacklocal cluster.local
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 172.16.120.98
# cat /etc/dnsmasq.d/origin-dns.conf
no-resolv
domain-needed
no-negcache
max-cache-ttl=1
enable-dbus
dns-forward-max=5000
cache-size=5000
bind-dynamic
except-interface=lo
# End of config
# cat /etc/dnsmasq.d/origin-upstream-dns.conf
server=172.16.120.11
server=172.16.120.2
server=172.16.120.3
4) ##S2I build successfully
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188 |