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.

This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/f6ae947b3e66623fa7d51082297c2acd5cbe8c88/

this seems to be present in 7.5

*** Bug 1560502 has been marked as a duplicate of this bug. ***

Hi Vlad,

Does this still happen on our CI?

Thanks!
Sushil

Go to the link in the fist comment, it happened for the last time on 1.10.2-12.el7 but just on s390x. I don't think we have different version now in 7.5 (as just minor z stream fixes landed since then).
So I would say it is present. Guys, ideas?

Clicking on "Show versions" button in the first link shows:

 1:1.10.2-14.el7_5
 1:1.10.2-13.el7
 1:1.10.2-12.el7

So, I would say this is still present on RHEL 7.5. However it is not clear to me how to reproduce the issue, and I couldn't find how the assertion could be hit.

*** Bug 1591188 has been marked as a duplicate of this bug. ***

Hi Vlad,

Could you please retry this on 7.6?

Thanks!
Sushil

haven't seen this on 7.6 will reopen if it occurs again.