Bug 212791 - FC5=>FC6 upgrade replaced ntp.conf with default stub
FC5=>FC6 upgrade replaced ntp.conf with default stub
Product: Fedora
Classification: Fedora
Component: ntp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Miroslav Lichvar
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-10-28 23:19 EDT by John Bass
Modified: 2008-08-02 19:40 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 12:36:24 EDT
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 John Bass 2006-10-28 23:19:45 EDT
Description of problem: Upgrade replaced ntp.conf with a default stub file,
effectively disabling ntp on the production server after the upgrade. Upgrades
should install new default stub files as .rpmnew. In cases where substantial
changes are made in file formats, script editing during the update to correct is
preferred over disabling the system.

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

How reproducible:
Appears to be always, did both our servers.

Steps to Reproduce:
1. CDROM upgrade from FC5 to FC6
Actual results:
ntp server was effectively disabled by the upgrade.

Expected results:
upgrade should leave server functional, as before, unless unaviodable version
skew is created.

Additional info:
Comment 1 Miroslav Lichvar 2006-10-30 08:33:45 EST
The ntp.conf file is marked as noreplace, so it shouldn't be replaced unless it
is the original file from the old package.

Was the ntp.conf file modified? Or problem is that the new default config isn't
working correctly, but the old default config was?
Comment 2 Bug Zapper 2008-04-04 00:13:17 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 3 Bug Zapper 2008-05-06 12:36:22 EDT
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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