Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 228140

Summary: ntpd ignores servers not yet visible due to NetworkManager
Product: [Fedora] Fedora Reporter: Stefan Becker <chemobejk>
Component: ntpAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 6   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-02-10 09:22:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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.