Bug 1100794 - New dispatcher script does not work with python2
Summary: New dispatcher script does not work with python2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dnssec-trigger
Version: 20
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Pavel Šimerda (pavlix)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1101041 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-23 12:58 UTC by Tomáš Hozza
Modified: 2014-09-19 10:07 UTC (History)
5 users (show)

Fixed In Version: dnssec-trigger-0.12-13.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-19 10:07:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
fix (1.22 KB, patch)
2014-06-03 17:09 UTC, Pavel Šimerda (pavlix)
no flags Details | Diff

Description Tomáš Hozza 2014-05-23 12:58:31 UTC
Description of problem:
The previous version of dispatcher script (in 0.11) worked well with Python2
and there was also explicit version of python used when running the script
#!/usr/bin/python2 instead of #!/usr/bin/python (which might point to a different
version of python on different versions of the system and distributions.

After upgrading to the latest 0.12 version the script ends with traceback:

# python /usr/libexec/dnssec-trigger-script --update
Traceback (most recent call last):
  File "/usr/libexec/dnssec-trigger-script", line 435, in <module>
    Application(sys.argv).run()
  File "/usr/libexec/dnssec-trigger-script", line 349, in run
    self.method()
  File "/usr/libexec/dnssec-trigger-script", line 382, in run_update
    self.run_update_global_forwarders()
  File "/usr/libexec/dnssec-trigger-script", line 391, in run_update_global_forwarders
    servers = Store('servers')
  File "/usr/libexec/dnssec-trigger-script", line 258, in __init__
    except FileNotFoundError:
NameError: global name 'FileNotFoundError' is not defined

Version-Release number of selected component (if applicable):
dnssec-trigger-0.12-1.fc20.x86_64

How reproducible:
Always

Comment 1 Pavel Šimerda (pavlix) 2014-05-25 13:20:54 UTC
Forgot to test upstream with Python2...

Comment 2 Tomáš Hozza 2014-05-26 06:40:53 UTC
*** Bug 1101041 has been marked as a duplicate of this bug. ***

Comment 3 Pavel Šimerda (pavlix) 2014-06-03 17:09:52 UTC
Created attachment 901863 [details]
fix

Comment 4 Pavel Šimerda (pavlix) 2014-06-03 17:10:40 UTC
It has been sent upstream as well.

Comment 5 Pavel Šimerda (pavlix) 2014-06-06 17:10:49 UTC
Fixed in rawhide, we'll issue an update for F20 when ready.

Comment 6 Fedora Update System 2014-06-30 15:30:15 UTC
dnssec-trigger-0.12-12.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/dnssec-trigger-0.12-12.fc20

Comment 7 Fedora Update System 2014-07-01 07:21:55 UTC
Package dnssec-trigger-0.12-12.fc20:
* should fix your issue,
* was pushed to the Fedora 20 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-12.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-7942/dnssec-trigger-0.12-12.fc20
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2014-08-11 11:40:46 UTC
dnssec-trigger-0.12-13.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/dnssec-trigger-0.12-13.fc20

Comment 9 Fedora Update System 2014-09-19 10:07:07 UTC
dnssec-trigger-0.12-13.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


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