Bug 2238248

Summary: ABRT can't submit crash report: processing failed
Product: [Fedora] Fedora Reporter: Ben <ben>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 38CC: abrt-devel-list, abrt-sig, marcan, michal.toman, msrb, teohhanhui
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-31 08:28:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
requested problem.txt file none

Description Ben 2023-09-10 21:35:39 UTC
Description of problem:

ABRT reports an error when trying to submit a bug report to the Bugzilla server. I have entered a valid Bugzilla API key obtained from bugzilla.redhat.com.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Enter valid API key into ABRT
2. Attempt to submit crash report by clicking the blue "Report" button
3. Observe error message in pop-up window under "show log"

Actual results:
--- Running report_uReport ---
Server responded with an error: 'Element 'os' is invalid: Element 'name' is invalid: Only the following values are allowed: centos, fedora'
('report_uReport' exited with 1)

Expected results:
It should submit the crash report successfully.


Additional info:

Comment 1 Michal Srb 2023-09-11 06:31:05 UTC
Thanks for the bug report.

Could you please share the output of the reporter-ureport command? If you go to the directory where the problem is located (/var/spool/abrt/<problem-dir>/) and type:

$ reporter-ureport -vvv . > ~/problem.txt 2>&1

And then upload the problem.txt file from your home direcotory here please? Thanks!

Comment 2 Hector Martin 2023-09-11 14:57:25 UTC
Relevant: https://pagure.io/fedora-asahi/project/issue/20

> ABRT doesn't know `fedora-asahi-remix` os-release ID

Comment 3 Ben 2023-09-12 01:01:12 UTC
Created attachment 1988234 [details]
requested problem.txt file

Comment 4 Aoife Moloney 2024-05-31 08:28:37 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.