Bug 82148

Summary: firstboot fails after fresh install
Product: [Retired] Red Hat Linux Reporter: Ulrich Drepper <drepper>
Component: firstbootAssignee: Brent Fox <bfox>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:51:14 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 Ulrich Drepper 2003-01-18 06:44:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030117

Description of problem:
After a completely fresh install upon the first boot, firstboot fails.  A window
with firstboot.py in the tital pops up and reads:

Traceback (most recent call list):
 File "/usr/share/fistboot/firstbootWindow.py", line 153, in __init__
  vbox, eventbox = module.launch()
 File "/usr/share/firstboot/modules/data.py", line 75, in launch
  self.setupScreen()
 File "/usr/share/firstboot/modules/data.py", line 64, in setUpScreen
  self.dataPage = data_gui.datePage(self.dataBackend)
 File "/usr/share/redhat-config-data/data_gui.py", line 171, in __init__
  ntpServer = socket.gethostbyaddr(ntpServerIP)[0]
TypeError: gethostbyaddr() argument 1 must be string, not None


Since there is a problem with the Data and Time module,
Red Hat Setup Agent will not load this module and
will attempt to run the remaining modules.

Please file a bug [...]


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


How reproducible:
Didn't try

Steps to Reproduce:
1.Fresh install.
2.Reboot
3.
    Is there something about ntp versions in the installer?  I don't
think I've selected anything.

Actual Results:  Above message in a window

Expected Results:  firstboot GUI

Additional info:

Comment 1 Brent Fox 2003-01-18 17:40:52 UTC
No, nothing wrong with ntp.  It was a bug on my part in redhat-config-date.

*** This bug has been marked as a duplicate of 82061 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:51:14 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.