Description of problem: On Fedora 36 Beta RC, Anaconda is unable to report crashes to Bugzilla. The process ends up with the following error: --- Running report_Bugzilla --- Checking for duplicates fatal: Unable to make sense of XML-RPC response from server. Invalid struct for <fault> value. Invalid value for 'faultCode' member. Value of type STRING supplied where type INT was expected.. Use XMLRPC_TRACE_XML to see for yourself ('report_Bugzilla' exited with 1) Version-Release number of selected component (if applicable): anaconda-36.16.2-2.fc36.x86_64 How reproducible: Always Steps to Reproduce: 1. Start the RC beta Live ISO 2. Start Anaconda, do some stuff and start the installation. 3. Crash it using the command: kill -USR1 `cat /var/run/anaconda.pid` 4. Use the built-in reporter to have report it. 5. Also, have you Bugzilla API_KEY ready, since you will not be able to send it without it. Actual results: A crash is impossible to report. Expected results: It should possible to report crashes.
Proposed as a Blocker for 36-beta by Fedora user lruzicka using the blocker tracking app because: This violates the Failure reporting criteria https://fedoraproject.org/wiki/Basic_Release_Criteria#Failure_reporting
Same is happening with the textual version of Anaconda. See screenshot.
Created attachment 1865995 [details] The error message shown by Anaconda. The screenshot of the bug reporting process showing the error in Anaconda's text regime.
The update testing libreport (libreport-2.17.1-1.fc36.x86_64) fixes this.
FEDORA-2022-eb9a49a622 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-eb9a49a622
+5 in https://pagure.io/fedora-qa/blocker-review/issue/669 , marking accepted.
FEDORA-2022-eb9a49a622 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.