Description of problem:
Version-Release number of selected component:
cmdline: /usr/bin/python3 /usr/libexec/dnssec-trigger-script --update
Traceback (most recent call last):
File "/usr/libexec/dnssec-trigger-script", line 634, in <module>
File "/usr/libexec/dnssec-trigger-script", line 414, in run
File "/usr/libexec/dnssec-trigger-script", line 563, in run_update
File "/usr/libexec/dnssec-trigger-script", line 627, in run_update_connection_zones
unbound_zones.add(zone, global_forwarders, secure=False)
File "/usr/libexec/dnssec-trigger-script", line 250, in add
self._commit(zone, set(servers), secure)
File "/usr/libexec/dnssec-trigger-script", line 278, in _commit
Local variables in innermost frame:
Created attachment 1006435 [details]
Created attachment 1006436 [details]
*** Bug 1206825 has been marked as a duplicate of this bug. ***
Thank you for this report.
This is a bug in the dnssec-trigger Python script. In case there is no connection available, meaning there are no global forwarders, then the script
tries to configure the RFC 1918 reverse zones and fails.
I'll prepare a patch.
Patch sent to the upstream. I'll push an update once they merge it.
dnssec-trigger-0.12-20.fc21 has been submitted as an update for Fedora 21.
dnssec-trigger-0.12-20.fc22 has been submitted as an update for Fedora 22.
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnssec-trigger-0.12-20.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dnssec-trigger-0.12-20.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
dnssec-trigger-0.12-20.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.