Bug 1936898

Summary:	Abrt cannot retrace any packages when trying to trace remotely.
Product:	[Fedora] Fedora	Reporter:	Lukas Ruzicka <lruzicka>
Component:	abrt	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	34	CC:	abrt-devel-list, abrt-sig, jakub, jmilan, mgrabovs, michal.toman, mmarusak, msrb
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-06-22 12:56:29 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:
Bug Depends On:
Bug Blocks:	1939467

Description Lukas Ruzicka 2021-03-09 12:44:10 UTC

Description of problem:

Abrt claims not to be able to trace any packages from caught crashes. The only could be retraced locally. 

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

abrt-2.14.5-2.fc34.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Catch a crash with Abrt.
2. Try to retrace it remotelly.

Actual results:

Reports error.

Expected results:

Remote tracing works normally.

Additional info:

This is the error message:

(process:49751): GLib-Net-WARNING **: 13:42:45.781: Failed to download missing issuer certificate from Authority Information Access URI http://apps.identrust.com/roots/dstrootcax3.p7c: failed gnutls_x509_crt_import: ASN1 parser: Error in TAG.
Retrace server is unable to process package 'audacity-2.4.2-4.fc34.x86_64'.
Is it a part of official 'Fedora 34 (Workstation Edition Prerelease)' repositories?
Unknown package sent to Retrace server.

Comment 1 Michal Srb 2021-03-16 15:15:00 UTC

Added to the tracking bug.

Comment 2 Matej Grabovsky 2021-06-22 12:56:29 UTC

We have deployed an upgrade for Retrace Server yesterday which should fix this bug.

Please check and reopen this bug if the problem persists.