Bug 307019

Summary: yast2-dhcpserver doesn't work
Product: [openSUSE] openSUSE 10.3 Reporter: Joop Boonen <joop.boonen>
Component: YaST2Assignee: Katarina Machalkova <kmachalkova>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: jdsn
Version: Beta 2   
Target Milestone: ---   
Hardware: Other   
OS: openSUSE 10.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: DHCP_Server_Configuration_error (Error Cannot determine the hostname of . )
save_y2logs /tmp/y2logs.tgz

Description Joop Boonen 2007-09-01 10:09:23 UTC
When starting up yast2 dhcpserver setup i get an error.

This is the xmessage screen:
Use of uninitialized value in substitution iterator at
        /usr/lib/perl5/vendor_perl/5.8.8/i586-linux-thread-multi/YaST/YCP.pm line 261 (#1)
    (W uninitialized) An undefined value was used as if it were already
    defined.  It was interpreted as a "" or a 0, but maybe it was a mistake.
    To suppress this warning assign a defined value to your variables.
    
    To help you figure out what was undefined, perl tells you what operation
    you used the undefined value in.  Note, however, that perl optimizes your
    program and the operation displayed in the warning may not necessarily
    appear literally in your program.  For example, "that $foo" is
    usually optimized into "that " . $foo, and the warning will refer to
    the concatenation (.) operator, even though there is no . in your
    program.
Comment 1 Joop Boonen 2007-09-01 10:13:17 UTC
Created attachment 161355 [details]
DHCP_Server_Configuration_error (Error Cannot determine the hostname of . )

Error
Cannot determine the hostname of .
Comment 2 Katarina Machalkova 2007-09-03 13:49:42 UTC
Please attach y2logs (http://en.opensuse.org/Bugs/YaST)
Comment 3 Joop Boonen 2007-09-03 20:34:05 UTC
Created attachment 161571 [details]
save_y2logs /tmp/y2logs.tgz

save_y2logs /tmp/y2logs.tgz
Comment 4 Katarina Machalkova 2007-09-04 08:32:23 UTC
Hmm :( 
What does '/bin/hostname --short' and '/bin/hostname --fqdn' print (if you run those from shell)? Seems that at least one of these two fail on your machine for so far unknown reason.

Anyway, even if dhcp server module does not succeed in getting hostname, it should not abort. Unless you use LDAP for configuring DHCP, of course. In that case having the right hostname available is absolutely necessary.
Comment 5 Joop Boonen 2007-09-04 17:57:36 UTC
This is the output both as a user and as root

jboonen@centrino:~> /bin/hostname --short
hostname: Unknown host
jboonen@centrino:~> /bin/hostname --fqdn
hostname: Unknown host
jboonen@centrino:~> su -
Password:
centrino:~ # /bin/hostname --short
hostname: Unknown host
centrino:~ # /bin/hostname --fqdn
hostname: Unknown host
centrino:~ #

By the way I'm not using ldap. 
Comment 6 Joop Boonen 2007-09-04 17:59:53 UTC
By the way without aguments it finds the hostname.

centrino:~ # /bin/hostname
centrino
centrino:~ # exit
logout
jboonen@centrino:~> /bin/hostname
centrino
jboonen@centrino:~>
Comment 7 Katarina Machalkova 2007-09-06 17:29:37 UTC
.
Comment 8 Katarina Machalkova 2007-09-07 17:51:02 UTC
Fixed in yast2-dhcp-server 2.15.5
Now if the hostname cannot be found, the module will start normally, only LDAP support cannot be activated.