Support #11720
closed
fetching kickstart fails while provisioning process
Description
Hello,
i wanted to provision a new host with CentOS 7.
The host loaded the image from the mirror successfully.
But it stops provisioning when fetching the "Kickstart" template.
You can see this on the screenshot i attached.
After a few minutes I can execute commands with the user "dracut".
I think it's a dns-problem of my new host, because he doesn't know my foreman-server.
But otherwise DHCP gives the IP from the DNS -> there's an entry for my foreman-server, but the host doesn't know him anyway.
Any idea?
Here are some log messages from foreman-proxy.
They're looking ok, i think.
I, [2015-09-08T11:19:45.955392 #1384] INFO -- : Enumerated hosts on 192.168.10.64 D, [2015-09-08T11:19:45.955471 #1384] DEBUG -- : Lazy loaded 192.168.10.64/255.255.255.192 records D, [2015-09-08T11:19:45.956333 #1384] DEBUG -- : Searching for free IP - pinging 192.168.10.101 D, [2015-09-08T11:19:47.978929 #1384] DEBUG -- : Found free IP 192.168.10.101 out of a total of 62 free IPs 192.168.10.90 - - [08/Sep/2015 11:19:47] "GET /dhcp/192.168.10.64/unused_ip HTTP/1.1" 200 23 2.0317 D, [2015-09-08T11:20:25.714427 #1384] DEBUG -- : verifying remote client 192.168.10.90 against trusted_hosts ["voss-centos1.example.local", "192.168.10.90"] D, [2015-09-08T11:20:25.715313 #1384] DEBUG -- : running /usr/bin/nsupdate -k /etc/foreman.key D, [2015-09-08T11:20:25.725494 #1384] DEBUG -- : nsupdate: executed - server 127.0.0.1 D, [2015-09-08T11:20:25.729538 #1384] DEBUG -- : nsupdate: executed - update add 101.10.168.192.in-addr.arpa. 86400 IN PTR foremanvm.example.local 192.168.10.90 - - [08/Sep/2015 11:20:25] "POST /dns/ HTTP/1.1" 200 - 0.0983 D, [2015-09-08T11:20:25.886945 #1384] DEBUG -- : verifying remote client 192.168.10.90 against trusted_hosts ["voss-centos1.example.local", "192.168.10.90"] 192.168.10.90 - - [08/Sep/2015 11:20:25] "GET /tftp/serverName HTTP/1.1" 200 30 0.0017 D, [2015-09-08T11:20:26.025718 #1384] DEBUG -- : verifying remote client 192.168.10.90 against trusted_hosts ["voss-centos1.example.local", "192.168.10.90"] D, [2015-09-08T11:20:26.026398 #1384] DEBUG -- : Reading config file /etc/dhcp/dhcpd.conf D, [2015-09-08T11:20:26.026598 #1384] DEBUG -- : Reading config file /etc/dhcp/dhcpd.hosts D, [2015-09-08T11:20:26.026685 #1384] DEBUG -- : Reading config file /var/lib/dhcpd/dhcpd.leases D, [2015-09-08T11:20:26.026906 #1384] DEBUG -- : Loading subnets for 127.0.0.1 D, [2015-09-08T11:20:26.027307 #1384] DEBUG -- : Added 192.168.10.64/255.255.255.192 to 127.0.0.1 D, [2015-09-08T11:20:26.027810 #1384] DEBUG -- : Loading subnet data for 192.168.10.64/255.255.255.192 D, [2015-09-08T11:20:26.028750 #1384] DEBUG -- : Added provisiontest.example.local (192.168.10.98 / ee:00:eb:ec:40:7c) to 192.168.10.64/255.255.255.192 D, [2015-09-08T11:20:26.029260 #1384] DEBUG -- : Added provisiontest.example.local (192.168.10.98 / ee:00:eb:ec:40:7c) to 192.168.10.64/255.255.255.192 D, [2015-09-08T11:20:26.029588 #1384] DEBUG -- : Added foremantest.example.local (192.168.10.100 / ba:17:1d:4b:f5:32) to 192.168.10.64/255.255.255.192 I, [2015-09-08T11:20:26.030355 #1384] INFO -- : Enumerated hosts on 192.168.10.64 D, [2015-09-08T11:20:26.030429 #1384] DEBUG -- : Lazy loaded 192.168.10.64/255.255.255.192 records D, [2015-09-08T11:20:26.030526 #1384] DEBUG -- : Added foremanvm.example.local (192.168.10.101 / ce:b7:de:a3:77:dc) to 192.168.10.64/255.255.255.192 D, [2015-09-08T11:20:26.047748 #1384] DEBUG -- : omshell: executed - set name = "foremanvm.example.local" D, [2015-09-08T11:20:26.048174 #1384] DEBUG -- : true D, [2015-09-08T11:20:26.048247 #1384] DEBUG -- : omshell: executed - set ip-address = 192.168.10.101 D, [2015-09-08T11:20:26.048283 #1384] DEBUG -- : true D, [2015-09-08T11:20:26.048329 #1384] DEBUG -- : omshell: executed - set hardware-address = ce:b7:de:a3:77:dc D, [2015-09-08T11:20:26.048365 #1384] DEBUG -- : true D, [2015-09-08T11:20:26.048408 #1384] DEBUG -- : omshell: executed - set hardware-type = 1 D, [2015-09-08T11:20:26.048454 #1384] DEBUG -- : true D, [2015-09-08T11:20:26.049194 #1384] DEBUG -- : omshell: executed - set statements = "filename = \"pxelinux.0\"; next-server = c0:a8:0a:5a; option host-name = \"foremanvm.example.local\";" D, [2015-09-08T11:20:26.049386 #1384] DEBUG -- : true D, [2015-09-08T11:20:26.049432 #1384] DEBUG -- : omshell: executed - create D, [2015-09-08T11:20:26.049468 #1384] DEBUG -- : true I, [2015-09-08T11:20:26.133611 #1384] INFO -- : Added DHCP reservation for foremanvm.example.local (192.168.10.101 / ce:b7:de:a3:77:dc) 192.168.10.90 - - [08/Sep/2015 11:20:26] "POST /dhcp/192.168.10.64 HTTP/1.1" 200 - 0.1101 D, [2015-09-08T11:20:26.453634 #1384] DEBUG -- : verifying remote client 192.168.10.90 against trusted_hosts ["voss-centos1.example.local", "192.168.10.90"] I, [2015-09-08T11:20:26.454973 #1384] INFO -- : TFTP: entry for ce:b7:de:a3:77:dc created successfully 192.168.10.90 - - [08/Sep/2015 11:20:26] "POST /tftp/syslinux/ce:b7:de:a3:77:dc HTTP/1.1" 200 - 0.0031 D, [2015-09-08T11:20:26.567165 #1384] DEBUG -- : verifying remote client 192.168.10.90 against trusted_hosts ["voss-centos1.example.local", "192.168.10.90"] D, [2015-09-08T11:20:26.568475 #1384] DEBUG -- : Starting task: /usr/bin/wget --timeout=10 --tries=3 --no-check-certificate -nv -c "http://mirror.centos.org/centos/7/os/x86_64/images/pxeboot/vmlinuz" -O "/var/lib/tftpboot/boot/CentOS-7.1-x86_64-vmlinuz" 192.168.10.90 - - [08/Sep/2015 11:20:26] "POST /tftp/fetch_boot_file HTTP/1.1" 200 - 0.0162 D, [2015-09-08T11:20:26.687951 #1384] DEBUG -- : verifying remote client 192.168.10.90 against trusted_hosts ["voss-centos1.example.local", "192.168.10.90"] D, [2015-09-08T11:20:26.689709 #1384] DEBUG -- : Starting task: /usr/bin/wget --timeout=10 --tries=3 --no-check-certificate -nv -c "http://mirror.centos.org/centos/7/os/x86_64/images/pxeboot/initrd.img" -O "/var/lib/tftpboot/boot/CentOS-7.1-x86_64-initrd.img" 192.168.10.90 - - [08/Sep/2015 11:20:26] "POST /tftp/fetch_boot_file HTTP/1.1" 200 - 0.0175
Files
Updated by Dominic Cleal over 8 years ago
- Status changed from New to Feedback
Lukas Müller wrote:
I think it's a dns-problem of my new host, because he doesn't know my foreman-server.
But otherwise DHCP gives the IP from the DNS -> there's an entry for my foreman-server, but the host doesn't know him anyway.
The error message in the screenshot certainly indicates a DNS issue, could not resolve host.
Use dig to check if your DNS server is responding properly, e.g. dig voss-centos1.example.local @1.2.3.4 (where 1.2.3.4 is your DNS server). Double check which DNS server(s) the DHCP server's configured for.
Updated by Lukas Müller over 8 years ago
The answer is ok.
; <<>> DiG 9.9.6-P1 <<>> voss-centos1.example.local@192.168.10.90 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31780 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;voss-centos1.example.local\@192.168.10.90. IN A ;; AUTHORITY SECTION: . 847 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2015090800 1800 900 604800 86400 ;; Query time: 0 msec ;; SERVER: 10.140.79.240#53(10.140.79.240) ;; WHEN: Tue Sep 08 12:29:18 CEST 2015 ;; MSG SIZE rcvd: 144
The DNS-Servers which are configured in my provisioning config is the one i prooved with the command above and another one as secondary dns in my network.
Updated by Dominic Cleal over 8 years ago
There's no answer in your query, it's not OK. You're also missing a space between the name and "@" symbol in the command, which will also stop it working.
Updated by Lukas Müller over 8 years ago
I got the same output with the space between the name and "@".
Updated by Dominic Cleal over 8 years ago
It ought to be different as it'll be doing a very different thing. If there's no answer included though, then your DNS server is misconfigured somehow and isn't responding to the hostname of the Foreman server - you'll need to fix it.
Updated by Lukas Müller over 8 years ago
ok, i'm going to proof the dns answers.
Thank's for you help.
I will give feedback, if i can fix it.
Updated by Lukas Müller over 8 years ago
I had to add a forward dns entry for the foreman machine.
The vm could resolve the hostname now and started to download.
Hope it runs now.
Updated by Dominic Cleal over 8 years ago
- Status changed from Feedback to Resolved
Thanks for confirming.