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.
DescriptionMartin Kletzander
2021-04-13 08:19:29 UTC
Description of problem:
Originally filed upstream as https://gitlab.gnome.org/GNOME/glib/-/issues/2031 because this issue causes libvirtd to crash in some cases. It became more urgent with RHV upgrade to newer RHEL where libvirt started using glib and the crashes from layered products are now happening more and more often.
There are some workarounds for this in the libvirt codebase (see e.g. Bug 1894045, Bug 1931331, and their backports) but there are two issues with those:
- the code is noticeably slower than without the workarounds
- we are unsure if the workarounds handle all possible issues as more glib-related crashers are coming our way
Since this has been fixed upstream with https://gitlab.gnome.org/GNOME/glib/-/merge_requests/1353 in 2.64.0, and if I recall correctly also backported to 2.62.2, possibly also some other versions, it would be really helpful to have these fixes in, especially for our layered products, be it by backporting or rebasing.
Version-Release number of selected component (if applicable):
glib2-2.56.4-8.el8.x86_64
How reproducible:
Couple of times per day with layered products such as RHV
Additional info:
Latest repetition of this is *probably* Bug 1945940, which again points to similar issue.
Comment 1Michael Catanzaro
2021-04-13 13:08:13 UTC
Sure.
Looks like this is important enough to go to 8.4.z rather than wait for 8.5. Do you agree?
Comment 3Michael Catanzaro
2021-04-13 13:10:15 UTC
Reading more closely, looks like you have workarounds for this already, and 8.5 will probably suffice?
Comment 4Martin Kletzander
2021-04-14 12:40:03 UTC
8.4 would be more preferable, we are fixing the issues even in 8.3.1.z due to RHV having issues daily due to this. Yes, we have workarounds, but they are slower.
Comment 5Martin Kletzander
2021-04-14 12:44:48 UTC
If, however, the backport is too risky, then rebase in 8.5 will have to suffice, I hope we will not get many new bug reports until then.
Comment 11Michael Catanzaro
2021-05-05 20:39:44 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 (Moderate: glib2 security and bug fix update), 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/RHSA-2021:4385