Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1880939 - did does not recognise the errata plugin
Summary: did does not recognise the errata plugin
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: did
Version: 33
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Petr Šplíchal
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-09-21 08:00 UTC by Karel Volný
Modified: 2020-09-24 14:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

Description Karel Volný 2020-09-21 08:00:19 UTC
Description of problem:
After upgrading to F33, did stopped working. It complains about missing errata plugin.

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

How reproducible:

Steps to Reproduce:
1. have a setup which utilises the errata plugin
2. run did

Actual results:
[kvolny@kvolny 2020]$ did last week > 2020-38
[ERROR] Invalid plugin type 'errata' in section 'errata'.

Expected results:
(no such error, status report is generated)

Additional info:
[kvolny@kvolny 2020]$ rpm -ql qa-tools-workstation | grep plugins/errata

Comment 1 Karel Volný 2020-09-24 14:45:09 UTC
it magically started working again ...

what might be relevant:

* I've installed python3-fmf - probably, qa-tools-workstation should depend on this

* I've rebuilt from sources and reinstalled beaker and rhts packages (particularly rhts-python subpackage is affected by python 3.8 -> 3.9 change that happened during F33 devel cycle)

* I've patched some python 3.9 incompatibilities on my system (after the tools thrown traceback)

probably, something of the above led to errata module not being able to load cleanly in did - I leave this bug open, not closing "worksforme", for consideration whether did could report a better error message, leading to the root cause of the problem, instead of just pretending that the "plugin type" errata doesn't exist

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