ERF50-9294 » History » Version 9
Lukas Zapletal, 09/17/2018 12:34 PM
1 | 1 | Lukas Zapletal | h1. ERF50-9294 Failed to save: failed to detect boot server |
---|---|---|---|
2 | |||
3 | 3 | Daniel Moessner | <pre> |
4 | 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) |
5 | 3 | Daniel Moessner | </pre> |
6 | 1 | Lukas Zapletal | |
7 | 3 | Daniel Moessner | <pre> |
8 | failed to detect boot server: ERF50-9294 [Foreman::WrappedException]: Unable to find IP address for 'capsule-server.satellite.example.com' ([SocketError]: getaddrinfo: Name or service not known) |
||
9 | </pre> |
||
10 | 1 | Lukas Zapletal | |
11 | 8 | Lukas Zapletal | This happens when the 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. |
12 | 1 | Lukas Zapletal | |
13 | 8 | Lukas Zapletal | By default, Foreman explicitly contacts DNS servers configured in the SOA therefore it ignores system-wide DNS setting (like @resolv.conf@, @/etc/hosts@, etc). This can lead to issues and may be unexpected behaviour for some administrators. |
14 | 1 | Lukas Zapletal | |
15 | 8 | Lukas Zapletal | To change this the following options are available: |
16 | 2 | Lukas Zapletal | |
17 | 8 | Lukas Zapletal | * Change the global setting @Administer -> Settings -> Provisoning -> Query local nameservers@ via Web UI. Foreman will then query the locally configured resolver instead of the SOA/NS authorities when the setting is set. Note it will use that setting also for checking for DNS conflicts when creating new hosts. |
18 | 1 | Lukas Zapletal | |
19 | 8 | Lukas Zapletal | * Or set the @tftp_servername@ configuration value to the server's IP address instead of the DNS name, directly in @/etc/foreman-proxy/settings.d/tftp.yml@, so Foreman won't need to resolve the hostname: |
20 | 3 | Daniel Moessner | |
21 | 8 | Lukas Zapletal | <pre> |
22 | [root@myproxy ~]# cat /etc/foreman-proxy/settings.d/tftp.yml |
||
23 | --- |
||
24 | :enabled: true |
||
25 | :tftproot: /var/lib/tftpboot/ |
||
26 | :tftp_servername: 192.168.99.1 |
||
27 | </pre> |
||
28 | 2 | Lukas Zapletal | |
29 | 8 | Lukas Zapletal | * *restart @foreman-proxy@* process after changing by issuing @# service foreman-proxy restart@ |
30 | 6 | Daniel Moessner | |
31 | 8 | Lukas Zapletal | * Foreman installer can set this automatically via @--foreman-proxy-tftp-servername@ option. |
32 | 9 | Lukas Zapletal | |
33 | This error also appears when no Subnet was selected for a Host or a Hostgroup. Make sure there is a Subnet selected before submitting Host form. |