Project

General

Profile

Actions
Copy link

Bug #12053

closed

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

Added by Sachin Ghai about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Discovery plugin
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_discovery/pull/222
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

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.

Files

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

Related issues 1 (0 open — 1 closed)

Related to Discovery - Tracker #10294: PXEless discovery featureClosedLukas Zapletal04/28/2015

Actions
Actions
Copy link

Also available in: Atom PDF