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.
Bug 1848493 - ABRT incorrectly deduplicates a class of Anaconda bugs
Summary: ABRT incorrectly deduplicates a class of Anaconda bugs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: python-meh
Version: 8.4
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Martin Kolman
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-18 13:09 UTC by Martin Kolman
Modified: 2021-12-18 07:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-18 07:26:57 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Kolman 2020-06-18 13:09:51 UTC 
Description of problem:
ABRT incorrectly deduplicates a class of Anaconda bugs based on incorrectly parsing the traceback, resulting in many bugs that should be reported separately to be reported as duplicates of s single bug.

Not only is this confusing & can result in important issues being missed, but this also results in debugging data loss as duplicates only receive a short summary of the issue but not the full log dump a separate new bug would get.

It looks like ABRT things the bugs are the same if the exception name is the same, even if the message is different, for example, from a couple "duplicates":

reason:         dasbus.error.DBusError: Input/output error during write on /dev/sdb
reason:         dasbus.error.DBusError: set_user_ssh_key: user tomas does not exist
reason:         dasbus.error.DBusError: [Errno 17] File exists: '/proc/self/mounts' -> '/mnt/sysroot/etc/mtab'

This can be seen in action on this Fedora bug, with many unrelated issues duped on a single bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1812727

As you can see, even if the exception is called the same, it is just a wrapper for very different issues and thus should not be lumped together into a single bug.

It is rather important to fix this, or else important install time customer issues on RHEL might be missed.

Upstrem ABRT issue tracking this can be found here: https://github.com/abrt/abrt/issues/1495
Comment 1 Vendula Poncova 2020-09-02 13:34:19 UTC 
We still see this issue in Fedora bugs. See: https://bugzilla.redhat.com/show_bug.cgi?id=1868577#c30
Comment 17 RHEL Program Management 2021-12-18 07:26:57 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.