Bug 1679314
| Summary: | [Dell EMC 7.6 BUG]: abrt fails to report bug due to tainted kernel | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Charles Rose (Dell) <crose> | ||||
| Component: | abrt | Assignee: | Martin Kyral <mkyral> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Kyral <mkyral> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 7.6 | CC: | ekulik, kazen, linux-bugs, mkyral, msuchy, ovasik | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 7.8 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | gnome-abrt-0.3.4-9.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 1791655 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-09-29 19:53:13 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1689420, 1729244, 1776446, 1780582, 1791655, 1824304 | ||||||
| Attachments: |
|
||||||
|
Description
Charles Rose (Dell)
2019-02-20 21:08:53 UTC
You should be able to report not-reportable (tainted) kernel oopses through terminal with: $ abrt-cli report --unsafe XXYYZZ This "feature" is not implemented in gnome-abrt yet. A workaround to report them with gnome-abrt is to delete a "not-reportable" file from problem directory (/var/spool/abrt/kerneloops-XX-YY-ZZ). Created attachment 1698049 [details]
screenshot of the dialog
Bugfix verified. gnome-abrt fires up a confirmation dialog allowing to proceed when attempting to report a not-reportable problem, instead of refusing it straight away (see the attached screenshot)
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (abrt bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3912 |