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
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