Project

General

Profile

ERF50-9294 » History » Version 2

Lukas Zapletal, 09/22/2016 03:31 AM
Elaborated the article

1 1 Lukas Zapletal
h1. ERF50-9294 Failed to save: failed to detect boot server
2 1 Lukas Zapletal
3 1 Lukas Zapletal
ERF50-9294 [Foreman::WrappedException]: Unable to find IP address for 'foreman.home.lan' ([Resolv::ResolvError]: DNS result has no information for foreman.home.lan)
4 1 Lukas Zapletal
5 2 Lukas Zapletal
This happens when hostname set in the tftp_servername option (TFTP Smart Proxy by default) has no valid DNS record via DNS servers set in SOA/NS record of the domain. Foreman resolves the hostname set in tftp_servername to an IP address in order to ensure clients boots without any DNS requests.
6 1 Lukas Zapletal
7 2 Lukas Zapletal
By default, Foreman explicitly contacts DNS servers configured in the SOA therefore it ignores system-wide DNS setting (resolv.conf, /etc/hosts etc). This can lead to issues and this may be unexpected behavior for some administrators.
8 2 Lukas Zapletal
9 2 Lukas Zapletal
Luckily, there is a global setting "Query local nameservers" available to change that behavior. Foreman will query the locally configured resolver instead of the SOA/NS authorities when the setting is set.
10 2 Lukas Zapletal
11 2 Lukas Zapletal
As an alternative, set the tftp_servername configuration value to IP address instead DNS name, therefore Foreman won't need to resolve the hostname.
12 2 Lukas Zapletal
13 2 Lukas Zapletal
The relevant setting can be found on the Smart Proxy (make sure to restart foreman-proxy process when changing):
14 2 Lukas Zapletal
15 1 Lukas Zapletal
<pre>
16 2 Lukas Zapletal
[root@myproxy ~]# cat /etc/foreman-proxy/settings.d/tftp.yml 
17 1 Lukas Zapletal
---
18 1 Lukas Zapletal
:enabled: true
19 1 Lukas Zapletal
:tftproot: /var/lib/tftpboot/
20 2 Lukas Zapletal
:tftp_servername: 192.168.99.1
21 1 Lukas Zapletal
</pre>
22 1 Lukas Zapletal
23 1 Lukas Zapletal
Foreman installer can set this automatically via @--foreman-proxy-tftp-servername@ option.