Bug 82384 - setting up /etc/ntp.conf before firstboot runs breaks date and time module
setting up /etc/ntp.conf before firstboot runs breaks date and time module
Status: CLOSED DUPLICATE of bug 82061
Product: Red Hat Linux
Classification: Retired
Component: firstboot (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Depends On:
  Show dependency treegraph
Reported: 2003-01-21 15:04 EST by Alexandre Oliva
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:51:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alexandre Oliva 2003-01-21 15:04:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
Running local configuration scripts at the end of kickstart or in single-user
mode, that modify /etc/ntp.conf, before firstboot runs can be fatal for the Date
and Time module.  Here's what my scripts append to the default /etc/ntp.conf:

# @AH_BEGIN:xntp.client:-rw-r-----    1 root     root          330 Aug 19 14:36
restrict nomodify notrap
restrict nomodify notrap
restrict nomodify notrap
restrict nomodify notrap
server # fri
server # fri-external
server # emilia
server # emilia-cipe
# @AH_END:xntp.client@

If I add this to /etc/ntp.conf and re-enable firstboot, the crash occurs just
the same.  The top of the anaconda stack trace is:

/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.

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

How reproducible:

Steps to Reproduce:
1.Add the lines above to /etc/ntp.conf
2.Let firstboot run

Actual Results:  The exception above.

Expected Results:  Should work, no?

Additional info:
Comment 1 Alexandre Oliva 2003-01-21 17:34:20 EST
Erhm.   I tried an install from scratch, without kickstart and without running
my scripts at first, and it failed just the same, so it has nothing to do with
my settings.
Comment 2 Brent Fox 2003-01-21 18:08:53 EST

*** This bug has been marked as a duplicate of 82061 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:17 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.