Fedora Account System
Red Hat Associate
Red Hat Customer
//EDIT: See comment 8 for a likely cause of the issue. While testing the Anaconda WebUI error reporting feature, I was able to trigger the error dialog and go through the Bugzilla reporting workflow, but after pressing the final "Report bug" button, nothing visible happened and no bug appeared to be created in Bugzilla. I am not completely sure where exactly the problem is. It could be in the WebUI reporting code, Bugzilla communication, or somewhere in between. The bug report seems to enter a black hole, but unfortunately without the interesting astrophysics. Reproducible: Always Steps to Reproduce: 1. Boot Fedora Workstation or KDE from a Live ISO. 2. Start Anaconda WebUI. 3. Select a language and press Continue. 4. Open a terminal and run sudo rm -f /run/anaconda/backend_ready 5. After the crash, fill in the API key. 6. Fill in some bug info and hit "Report bug" Actual Results: After pressing the button, no visible confirmation appeared and I could not find the newly created bug in Bugzilla. There was also no obvious error message shown by the UI. The last message from anaconda-webui in the journal before trying to submit the report was: anaconda-webui[5156]: ["ErrorBoundary caught an error:", {"contextData":{},"message":"The Anaconda installation has stopped unexpectedly."}] I did not see any later journal messages mentioning Bugzilla submission, a Bugzilla bug ID, or an explicit reporting failure. This does not necessarily mean that the reporting helper was not started, only that I did not find any useful trace of the submission in the available logs. Expected Results: After pressing "Report bug", Anaconda should create the Bugzilla report, preferably show some confirmation to the user, and the created bug should contain the expected description and attachments. Additional Information: Anaconda version: anaconda-45.22-1.fc45 The WebUI otherwise correctly notices removal of /run/anaconda/backend_ready and displays the error reporting dialog, so the first half of the error reporting test seems to work. It looks like the problem happens only near the final submission step. In other words, the bug reporter reports for duty, but possibly forgets to report the bug.
AGREED AcceptedBetaBlocker Discussed at the 2026-08-31 (blocker / freeze exception) review meeting: This is accepted as a clear violation of Basic criterion 'The installer must be able to report failures to Bugzilla, with appropriate information included'. https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-08-31/f45-blocker-review.2026-08-31-16.01.log.txt
I realized that my Bugzilla API key might have been revoked at the time of dealing with this, because when I tried to report via an http call, the server complained about an invalid API key. When I created a new one, Anaconda reported the bug as it should. However, in the above case, I deliberately tried an incorrect API key the first time and webUI would complain about it. When I used a seemingly "correct", the webUI did not complain about anything, it proceeded to the bug reporting page and behaved as described. Ergo, there is still some kind of bug, but does not have to be blockery anymore. We shall revote.
So I tested with correct key, which worked as expected, so yes probably revoked key on your side, but when I tried with revoked key, I got "The API key you specified has been revoked by the user that created it." which is correct as expected (Also tried revoking it after getting to reporting page, with same error result of it being revoked). Do I get it correctly that `seemengly "correct"` is revoked key ? (I also tried some made up keys which were detected correctly as false). So basically I could not reproduce this with revoked key.
Dropping AcceptedBlocker tag based on comment 2.
fedora 45 beta 1.3: tried my key and bz was filled: https://bugzilla.redhat.com/show_bug.cgi?id=2529325
Rejected as a Beta blocker. See https://forge.fedoraproject.org/quality/blocker-review/issues/2157
Created attachment 2156988 [details] reporting issue with expired API key. When I used an expired API key: After clicking the button, there was no visible confirmation. However, an error did occur — it was located at the top of the form. Its not visible and you have to scroll up. See the video for reference. Was this the issue?
Oh wow, that is super-sneaky. This clearly needs some UI improvements (at least scrolling the form to the top when an error happens).