RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
abrt detects kernel oops(amdgpu), but will not report to Red Hat due to tainted kernel (W). The kernel is tainted because sosreport ran 'bpftool' which is Tech Preview in RHEL 7.6 - https://access.redhat.com/solutions/3725951

As eBPF feature is unrelated to the kernel oops, abrt should allow the bug to be reported.

Version-Release number of selected component (if applicable):
abrt-2.1.11-52.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL7.6, wait for Kernel Oops
2. Click on abrt icon on gnome-desktop or 'abrt-cli list'
3. Bug cannot be reported to Red Hat due to tainted kernel.

Actual results:
A kernel problem occurred, but your kernel has been tainted (flags:GW). Explanation:
W - Taint on warning.
Kernel maintainers are unable to diagnose tainted reports.

"Report" button on abrt-gnome is disabled.

Expected results:
User should be able to report bug.

Additional info:

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