Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

On most of the rhel-9 supp rhel arches except for aarch64, I see a few run-backtrace testcase failures:

FAIL: run-backtrace-native.sh
FAIL: run-backtrace-native-biarch.sh
FAIL: run-backtrace-native-core.sh
FAIL: run-backtrace-native-core-biarch.sh

The aarch64 only suffers from:

FAIL: run-backtrace-native.sh
FAIL: run-backtrace-native-core.sh


This is easy to reproduce, so not providing more details for now, but can do if needed.

Versions:

elfutils-0.185-4.el9
glibc-2.34-1.el9

This is upstream bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=28190
Resolved with the following patch:
https://sourceware.org/pipermail/elfutils-devel/2021q3/004019.html
Already in Fedora:
https://src.fedoraproject.org/rpms/elfutils/blob/rawhide/f/elfutils-0.185-raise-pthread_kill-backtrace.patch

For unrelated reasons the rhel9 elfutils.spec file makes a failing testsuite test not fatal, so it currently doesn't cause FTBFS even with glibc 2.34 installed.

Patch in hand, but it is really just a testcase issue.
It won't fix the general issue of the testsuite being "flaky".
To solve that a rebase would be most appropriate.

Verified based on CI test results:
https://beaker.engineering.redhat.com/matrix/?toggle_nacks_on=on&job_ids=6027159

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 (new packages: elfutils), 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/RHBA-2022:3995