Bug 82526

Summary: firstboot: date and time module
Product: [Retired] Red Hat Linux Reporter: Jeff Gardner <jeff2712>
Component: firstbootAssignee: Brent Fox <bfox>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeff Gardner 2003-01-23 04:09:50 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030115

Description of problem:
Right after install, during which no bootloader was configured, I recieved a
request to submit a bug report concerning "firstboot." The d"Date and Time
Module" was unable to complete its mission. No bootloader was configured because
I prefer to put /path/to/phoebe/boot/vmlinuz???? in
/redHat8.0/boot/grub/grub.conf which resides on another partition.
An error message was generated in /root/firstboot.1043287811.31
It is copied below...




Version-Release number of selected component (if applicable):


How reproducible:
Didn't try


Additional info:

Here are the contents of /root/firstboot.1043287811.31

 Traceback (most recent call last):
  File "/usr/share/firstboot/firstbootWindow.py", line 153, in __init__
    vbox, eventbox = module.launch()
  File "/usr/share/firstboot/modules/date.py", line 75, in launch
    self.setupScreen()
  File "/usr/share/firstboot/modules/date.py", line 64, in setupScreen
    self.datePage = date_gui.datePage(self.dateBackend)
  File "/usr/share/redhat-config-date/date_gui.py", line 171, in __init__
    ntpServer = socket.gethostbyaddr(ntpServerIP)[0]
TypeError: gethostbyaddr() argument 1 must be string, not None
Comment 1 Bill Nottingham 2003-01-23 05:38:21 UTC 

*** This bug has been marked as a duplicate of 82061 ***
Comment 2 Red Hat Bugzilla 2006-02-21 18:51:20 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.