Bug 32442 - scan=hostname doesn't abort on unresolvable DNS name
scan=hostname doesn't abort on unresolvable DNS name
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UCS Installer
UCS 3.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Installer maintainers
:
Depends on: 29469
Blocks:
  Show dependency treegraph
 
Reported: 2013-08-30 19:34 CEST by Philipp Hahn
Modified: 2017-08-08 07:11 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2013-08-30 19:34:30 CEST
+++ This bug was initially created as a clone of Bug #29469 +++
During a PXE profile installation, the DNS server was not available. The host was named "3(NXDOMAIN)" instead:

# cat /tmp/installation_profile_scanned
hostname='3(NXDOMAIN)'

After the installation the host doesn't have any name:
# cat /etc/hostname

Looks like something (host) doesn't know the difference between STDOUT and STDERR...

+ for ts in '$to_scan' '$scan'
+ '[' hostname = hostname ']'
++ cat /proc/cmdline
++ grep ip
++ sed -e 's/.*ip=//g'
+ ipcmd='10.200.17.242:10.200.17.93:10.200.17.1:255.255.255.0 BOOTIF=01-e0-69-95-4f-81-0d BOOT_IMAGE=ucs-3.1-1/linux
++ echo 10.200.17.242:10.200.17.93:10.200.17.1:255.255.255.0 BOOTIF=01-e0-69-95-4f-81-0d BOOT_IMAGE=ucs-3.1-1/linux-
++ awk -F : '{print $1}'
+ myip=10.200.17.242
+ '[' -n '' ']'
+ '[' -n 192.168.0.135 ']'
++ host 10.200.17.242 192.168.0.135
++ tail -1
++ awk '{print $5}'
++ awk -F . '{print $1}'
+ host='3(NXDOMAIN)'
+ '[' -n '3(NXDOMAIN)' ']'
+ echo 'hostname='\''3(NXDOMAIN)'\'''

Please consider switching to "dig", which is the newer replacement for host:
# dig +short -x 10.200.17.242 @192.168.0.135
# dig +short -x 192.168.0.135 @192.168.0.135
xen12.phahn.dev.

In profile-mode the installer should probably abort the installer process, log an error message to a remote-log-server (Bug #19959) and power-off the computer.
In interactive mode, the profile should be marked as incomplete and the user should should get a chance to fix the hostname herself.
Comment 1 Philipp Hahn univentionstaff 2014-02-06 11:03:26 CET
again: this time with probably "no route to host" as the host is no called "no".
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:39:34 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Florian Best univentionstaff 2017-06-28 14:52:58 CEST
There is a Customer ID set so I set the flag "Enterprise Customer affected".
Comment 4 Stefan Gohmann univentionstaff 2017-08-08 07:11:25 CEST
This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.