Red Hat Bugzilla – Bug 1462825
Anconda bug reporting dialog is missing important log files & full traceback file
Last modified: 2017-07-06 18:51:18 EDT
Description of problem:
The bug reporting dialog in Anaconda is not including important log files, such as the full Anaconda traceback dump, anaconda.log, storage.log, program.log. etc.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start a F26 installation
2. perform https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_bugzilla
3. notice that the dialog where users can review what files will be uploaded to Bugzilla does not show any of the important Aanconda log files & the full traceback dump file
The full traceback file & important Anaconda log files are missing.
Full traceback file & important Anaconda log files are visible in the dialog.
The log files are present in /tmp as expected, including the anaconda-tb-* traceback dump file generated by python-meh.
As the Bugzilla upload dialog is provided by libreport it is possible this is caused by libreport changing how it includes log files in bugreports, so it is no longer picking up the Anaconda provided files.
Proposed as a Blocker for 26-final by Fedora user m4rtink using the blocker tracking app because:
Violation of the "Installer - Failure reporting" criterium:
"The installer must be able to report failures to Bugzilla, with appropriate information included."
Anaconda log files & the full traceback are certainly appropriate and indispensable information for successfully debugging of installer issues.
Discussed at 2017-06-26 blocker review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2017-06-26/f26-blocker-review.2017-06-26-16.03.html . Accepted as a blocker, as a violation of the criterion cited in #c1: we all agreed that this bug resulted in 'appropriate information' not being included in the report.
CCing Matej Habrnal, who seems to be dealing with libreport lately. Folks, this is an F26 Final blocker and we're in the Final freeze; someone needs to figure out what's going on here and fix it. I did try taking a look myself, but it's not something super obvious I could spot right away.
Martin, do you have any idea when this started happening? We could probably figure it out by just looking at all anaconda abrt reports for the last few months and spotting when the files stopped showing up, but if you happen to know, it'd save us the work...
Looking at the upstream libreport changelog, this change for 2.9.1 sounds possibly significant:
"Enhance the Bugzilla reporter to include only essential packaging details to make Bugzilla bug reports easier to comprehend."
I'm not sure what commits it relates to, yet.
Sorry, that change was in 2.9.0, which hit Rawhide (fc26 at the time) in December 2016.
anaconda-26.21.11-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-88f80a61da
anaconda-26.21.11-1.fc26, blivet-gui-2.1.5-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-88f80a61da
Verified the fix, see https://bugzilla.redhat.com/show_bug.cgi?id=1466965 .
anaconda-26.21.11-1.fc26, blivet-gui-2.1.5-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.