Bug 1880939 - did does not recognise the errata plugin
Summary: did does not recognise the errata plugin
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: did
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Šplíchal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-21 08:00 UTC by Karel Volný
Modified: 2021-11-30 16:24 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 16:24:56 UTC
Type: Bug
Embargoed:


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):
did-0.17-2.fc33.noarch

How reproducible:
always

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
/usr/lib/python3.9/site-packages/did/plugins/errata.py

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

Comment 2 Ben Cotton 2021-11-04 17:31:45 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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 EOL if it remains open with a
Fedora 'version' of '33'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 3 Ben Cotton 2021-11-30 16:24:56 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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.