Red Hat Bugzilla – Bug 219788
system-config-bind hangs when signing zone
Last modified: 2008-09-02 09:37:49 EDT
Description of problem:
Version-Release number of selected component (if applicable):
FC5, all updates as of 12/7/2006.
Steps to Reproduce:
1. start system-config-bind, and create a new zone 'test.dummy.', accepting all
2. right-click on 'test.dummy.' and select add->A record (ipv4), name
'a1.test.dummy.', ip 10.1.1.1
3. right click on 'test.dummy.' and select sign
1. 3 dialogs pop up (signing, gen zsk, gen ksk).
2. zkz dialog goes away.
3. ksk dialog goes away.
4. sigsning dialog stops pulsing, traceback to shell (see addl info, below), app
is now hung.
4. signing finishes, control returns to app.
Traceback (most recent call last):
File "/usr/share/system-config-bind/DNSsec.py", line 221, in
info.doneDialog.done( info.doneDialog, info.keyName, None )
File "/usr/share/system-config-bind/DNSsec.py", line 388, in SignZoneDialogDone
status, out = SignZoneWithKeys(info.bind, info.zone, info.ksk, info.zsk)
File "/usr/share/system-config-bind/DNSsec.py", line 320, in SignZoneWithKeys
File "/usr/share/system-config-bind/DNSsec.py", line 275, in EnableDNSSEC
if( (bind.version >= '9.3.0') and
File "/usr/share/system-config-bind/NamedConf.py", line 794, in __getitem__
Oops, forgot a few fields
Description of problem:
see bug title
tried twice, hung twice..
clarification: the signing dialog is hung. If you click on the window's close
box, the main app is ok. clicking save, quitting and restarting reveals that the
zone was created, as were the keys, and there is a signed zone file.
/etc/named.conf has been modified to include the signed zone file.
You're right, I can reproduce it here.
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
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
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.
Reopening for rawhide, still seems to hang.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
I can't reproduce it (to state of attached traceback) but the behaviour is still
bad - I get error dialog complaining about non existing zone file.
Solution(?): configuration has to be saved first before signing new zone.
Did you save it? I'm going to add save dialog (before trying to sign zone).
Seems to work for me.
Fixed. Closing in Rawhide. Wait for s-c-b update for F9 - it's not possible now due infrastructure problems.