Bug #12053
closed
foreman-server's hostname is not resolvable on provisioning a discovered host via pxeless
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 | ||
| error_couldnot_resolve_hostname.png | View error_couldnot_resolve_hostname.png | 34.9 KB | hostname resolution error | ||
| dbus_error.png | View dbus_error.png | 36.9 KB | some warning related to NM and Dbus error in another console | ||
| discovery_debug.txt | discovery_debug.txt | 55.2 KB | |||
| discovery_debug2.txt | discovery_debug2.txt | 55.8 KB | |||
| fetch_image.png | View fetch_image.png | 35.9 KB | fetched image before triggering provision | ||
| refetch_image.png | View refetch_image.png | 38 KB |
Updated by Sachin Ghai over 8 years ago
Updated by Sachin Ghai over 8 years ago
- Related to Tracker #10294: PXEless discovery feature added
Updated by Lukas Zapletal over 8 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.
Updated by Sachin Ghai over 8 years ago
- File discovery_debug.txt discovery_debug.txt added
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- Generated by NetworkManager
search xxxqe.lab.xxx.xxx.xxxx.com
nameserver 192.168.100.1
[root@fdi ~]# ping cloud-qe-15
PING cloud-qe-15.xxxqe.lab.xxx.xxx.xxxx.com (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.062 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.148 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=0.149 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=0.147 ms
^C
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.
Updated by Sachin Ghai over 8 years ago
- File discovery_debug2.txt discovery_debug2.txt added
discover-debug after making change to kexec. I can ping to server via hostname from discovered host
Updated by Sachin Ghai over 8 years ago
- File fetch_image.png fetch_image.png added
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.
Updated by Sachin Ghai over 8 years ago
- File refetch_image.png refetch_image.png added
I can fetched image even after triggering provisioning from webUI. Looks like still not able to catch the real issue.
Updated by The Foreman Bot over 8 years ago
- Status changed from Need more information to Ready For Testing
- Pull request https://github.com/theforeman/foreman_discovery/pull/222 added
- Pull request deleted (
)
Updated by Lukas Zapletal over 8 years ago
- Status changed from Ready For Testing to Closed