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.

This affects even libreport in rhel6 and makes the bugzilla plugin unusable. Patch is ready.

+++ This bug was initially created as a clone of Bug #820985 +++

After deliberately causing a failure in anaconda, reporting the first issue in partner-bugzilla works fine but causing the same failure a second time fails. The following log information is shown:

--- Running report_Bugzilla ---
Logging into Bugzilla at https://partner-bugzilla.redhat.com/
Checking for duplicates
fatal: (null)
(exited with 1)

At the time of this report, the partner-bugzilla duplicate is https://partner-bugzilla.redhat.com/show_bug.cgi?id=819676

If I report the same traceback multiple times to bugzilla.redhat.com, the log output on screen looks like:

--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Checking for duplicates
Bug is already reported: 820975
Logging out
Status: NEW https://bugzilla.redhat.com/show_bug.cgi?id=820975

My testing thus far has been with F17 final TC4. The exact procedure that I've been using to cause a failure in anaconda is as follows:
 1. boot DVD iso with the extra param:
   updates=http://tflink.fedorapeople.org/updates/f17_traceback.img
 2. proceed with installation until the timezone selection screen where a 
   traceback will happen
 3. Save the traceback to either bugzilla.redhat.com or 
    partner-bugzilla.redhat.com

QA-ACK for 6.3.0 Bugzilla was updated to v4.2 ABRT plugin needs to be updated too.

Drop blocking of F17.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Patch is ready and already used in Fedora.

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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0841.html