Bug 566840 - disabled dnssec-conf still mangles named.conf
Summary: disabled dnssec-conf still mangles named.conf
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dnssec-conf
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 505754 dnssecmods
TreeView+ depends on / blocked
 
Reported: 2010-02-19 22:23 UTC by John 'Warthog9' Hawley
Modified: 2010-06-28 15:41 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-06-28 15:41:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John 'Warthog9' Hawley 2010-02-19 22:23:21 UTC
Description of problem:
Explicitly disabling dnssecon-conf in /etc/sysconfig/dnssec mangles named.conf in much the same way as leaving it on does.

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

How reproducible:

Always

Steps to Reproduce:
1. Disable dnssec in /etc/sysconfig/dnssec
2. Restart named twice
3. *boom*
  
Actual results:

clean restart

Expected results:

config files to be parsed and modified (if it has to be) without it breaking the config

Additional info:

Comment 1 John 'Warthog9' Hawley 2010-02-19 22:25:09 UTC
Copying my post from bug#505754

even when "disabled" dnssec squashes
the named.conf config file.  This basically means my dns servers are failing
randomly as they get restarted for whatever reason (logrotate likely).  This is
beyond acceptable and I've started having to resort to more extreme measures to
keep dns running as expected.

diff from when dnssec is marked as "off" in /etc/sysconfig/dnssec

===================================================================
RCS file: RCS/named.conf,v
retrieving revision 1.98
diff -r1.98 named.conf
39c39,41
<         };
---
> 	dnssec-enable no;
> 	dnssec-validation no;
> };
53d54
< include "/etc/pki/dnssec-keys//dlv/dlv.isc.org.conf";
===================================================================

Which as you can imagine, puts the disabling lines in the wrong spot and causes
the restart to fail - yet again.

Comment 2 Bug Zapper 2010-04-28 11:52:45 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-06-28 15:41:04 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this 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.