Bug 1914170 - oops report contains abrt traceback
Summary: oops report contains abrt traceback
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 33
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
Assignee: Matej Grabovsky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-08 09:36 UTC by Petr Sklenar
Modified: 2021-11-30 17:45 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-11-30 17:45:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
abrt oops report (34.17 KB, application/octet-stream)
2021-01-08 09:36 UTC, Petr Sklenar
no flags Details

Description Petr Sklenar 2021-01-08 09:36:44 UTC
Created attachment 1745540 [details]
abrt oops report

Description of problem:
there is traceback in /usr/bin/abrt-action-check-oops-for-hw-error

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

How reproducible:
seen once

Steps to Reproduce:
1. oops report
2, look at logs in the attachment, don't know the cause


Actual results:
:Jan 07 10:13:03 kvm-03-guest13.lab.eng.rdu2.redhat.com abrt-server[70777]: Traceback (most recent call last):
:Jan 07 10:13:03 kvm-03-guest13.lab.eng.rdu2.redhat.com abrt-server[70777]:   File "/usr/bin/abrt-action-check-oops-for-hw-error", line 10, in <module>
:Jan 07 10:13:03 kvm-03-guest13.lab.eng.rdu2.redhat.com abrt-server[70777]:     from systemd import journal
:Jan 07 10:13:03 kvm-03-guest13.lab.eng.rdu2.redhat.com abrt-server[70777]: ModuleNotFoundError: No module named 'systemd'

Expected results:
no traceback of abrt in log

Additional info:

Comment 2 Matej Grabovsky 2021-01-20 14:58:47 UTC
The abrt-action-check-oops-for-hw-error crash has been fixed upstream: https://github.com/abrt/abrt/pull/1555

Comment 3 Ben Cotton 2021-11-04 16:16:03 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 4 Ben Cotton 2021-11-30 17:45:45 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.