Bug 1778921

Summary: elfutils debuginfod client not being called for stap/dwfl case
Product: Red Hat Enterprise Linux 8 Reporter: Frank Ch. Eigler <fche>
Component: elfutilsAssignee: Mark Wielaard <mjw>
elfutils sub component: system-version QA Contact: Martin Cermak <mcermak>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: mcermak, mjw, mnewsome
Version: 8.2Keywords: Bugfix, Triaged
Target Milestone: beta   
Target Release: 8.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: elfutils-0.178-6 Doc Type: No Doc Update
Doc Text:
No Doc Update
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:58:18 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:

Description Frank Ch. Eigler 2019-12-02 19:49:04 UTC
It appears the debuginfod_find_* calls are not being attempted for elfutils/libdwfl work related to the kernel:

% DEBUGINFOD_URLS=http://localhost/ stap -p2 -e 'probe kernel.function("do_exit") {}'

... generates no traffic to localhost if kernel-debuginfo* is not already installed.

Comment 1 Mark Wielaard 2019-12-05 16:56:11 UTC
Patch posted upstream: https://sourceware.org/ml/elfutils-devel/2019-q4/msg00234.html

Comment 2 Mark Wielaard 2019-12-11 15:26:17 UTC
The main fix is in upstream and the fedora elfutils-0.178-6 package already.
To get better diagnostics on download progress a patch is under discussion upstream
(a workaround for now would be to set the DEBUGINFOD_TIMEOUT env var to some large value).

Comment 3 Mark Wielaard 2019-12-13 22:55:26 UTC
Added first patch for the main bug. debuginfod progress/timeout fix might follow later.

Comment 8 errata-xmlrpc 2020-04-28 16:58:18 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1872