Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 228140 - ntpd ignores servers not yet visible due to NetworkManager
Summary: ntpd ignores servers not yet visible due to NetworkManager
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: ntp
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-02-10 09:01 UTC by Stefan Becker
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-02-10 09:22:56 UTC
Type: ---


Attachments (Terms of Use)

Description Stefan Becker 2007-02-10 09:01:15 UTC
Description of problem:

The correction of bug #216351 unfortunately doesn't fix the other ntpd problem
with NetworkManager: when ntpd starts up the interface isn't up and therefore
DNS lookups fail.


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

ntp-4.2.4-3.fc6


How reproducible: Always


Steps to Reproduce:
1. Boot up a machine configured to use NetworkManager
2.
3.

  
Actual results:

ntpd ignores configured NTP servers as the DNS lookup fails

Feb 10 10:13:57 baraddur ntpd[2007]: getaddrinfo: "0.fedora.pool.ntp.org"
invalid host address, ignored
Feb 10 10:13:57 baraddur ntpd[2007]: getaddrinfo: "1.fedora.pool.ntp.org"
invalid host address, ignored
Feb 10 10:13:57 baraddur ntpd[2007]: getaddrinfo: "2.fedora.pool.ntp.org"
invalid host address, ignored


Expected results:

ntpd should retry NTP server name resolution when server is flagged as "dynamic"

Comment 1 Stefan Becker 2007-02-10 09:22:56 UTC
Sorry, my bad. It seems I was not patient enough :-(

The new ntpd really retries server name resolution when a dynamic interface gets
activated.


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