Bug #12053

foreman-server's hostname is not resolvable on provisioning a discovered host via pxeless

Added by Sachin Ghai over 7 years ago. Updated over 7 years ago.

Discovery plugin
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:


foreman server's hostname is not resolvable when we provision a host that was discovered via pxeless. Provisioning stuck always at where host fetches the install.image from server. Please see the screen shot.

Also, I can see hostname resolution failures on other terminal(Alt+F3). Also some failures related to dbus. I'll close this if it will be a DNS setup/config issue.

unable_to_fetch_install_image.png View unable_to_fetch_install_image.png 20.4 KB error on fetching the install image from server Sachin Ghai, 10/05/2015 03:08 AM
error_couldnot_resolve_hostname.png View error_couldnot_resolve_hostname.png 34.9 KB hostname resolution error Sachin Ghai, 10/05/2015 03:11 AM
dbus_error.png View dbus_error.png 36.9 KB some warning related to NM and Dbus error in another console Sachin Ghai, 10/05/2015 03:13 AM
discovery_debug.txt discovery_debug.txt 55.2 KB Sachin Ghai, 10/06/2015 04:53 AM
discovery_debug2.txt discovery_debug2.txt 55.8 KB Sachin Ghai, 10/06/2015 10:21 AM
fetch_image.png View fetch_image.png 35.9 KB fetched image before triggering provision Sachin Ghai, 10/07/2015 06:05 AM
refetch_image.png View refetch_image.png 38 KB Sachin Ghai, 10/07/2015 06:07 AM
Unable to fetch install image Error couldnot resolve hostname Dbus error Fetch image Refetch image

Related issues

Related to Discovery - Tracker #10294: PXEless discovery featureClosed2015-04-28

Associated revisions

Revision ac51c0a6 (diff)
Added by Lukas Zapletal over 7 years ago

Refs #12053 - improved RHEL6 kexec template


#3 Updated by Sachin Ghai over 7 years ago

#4 Updated by Lukas Zapletal over 7 years ago

  • Status changed from New to Need more information

Sachin, can you log onto the image via ssh or console tty3 and investigate /etc/resolv.conf? Also show nmcli c show primary.

Were you provisioning with or w/o DHCP?

Ideally, attach discovery-debug output please.

#5 Updated by Sachin Ghai over 7 years ago

I can neither login to tty3 and nor can ssh once I triggered the provisioning. However, on discovered host, hostname is resolvable.

[root@fdi ~]# cat /etc/resolv.conf
  1. Generated by NetworkManager
    [root@fdi ~]# ping cloud-qe-15
    PING ( 56(84) bytes of data.
    64 bytes from icmp_seq=1 ttl=64 time=0.062 ms
    64 bytes from icmp_seq=2 ttl=64 time=0.148 ms
    64 bytes from icmp_seq=3 ttl=64 time=0.149 ms
    64 bytes from icmp_seq=4 ttl=64 time=0.147 ms

discovery-debug is from discovered host attached. Please note with PXE-based discovery I didn't find issue with hostname resolution. And In case of pxeless, Provisioning works if I change the server name with IP in the URL setup screen.

#6 Updated by Sachin Ghai over 7 years ago

discover-debug after making change to kexec. I can ping to server via hostname from discovered host

#7 Updated by Sachin Ghai over 7 years ago

Another update:

I replaced /usr/bin/kexec with dummy executable script. That holds the provisioning. here is the screen shot where I can fetch the image with server's hostname.

#8 Updated by Sachin Ghai over 7 years ago

I can fetched image even after triggering provisioning from webUI. Looks like still not able to catch the real issue.

#9 Updated by The Foreman Bot over 7 years ago

  • Status changed from Need more information to Ready For Testing
  • Pull request added
  • Pull request deleted ()

#10 Updated by Lukas Zapletal over 7 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF