Bug 1804171
Summary: | Fix major bug in primary keys handling | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Bastien Nocera <bnocera> |
Component: | gom | Assignee: | Bastien Nocera <bnocera> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 8.0 | CC: | tpelka, tpopela |
Target Milestone: | rc | Keywords: | Rebase |
Target Release: | 8.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gom-0.4-1.el8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-04 02:31:19 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
Bastien Nocera
2020-02-18 11:38:24 UTC
Bastien is there any way how to explicitly trigger the issue, or is there e.g. test within gom test suite that would test it? Thanks -Tom (In reply to Tomas Pelka from comment #1) > Bastien is there any way how to explicitly trigger the issue, or is there > e.g. test within gom test suite that would test it? There aren't any specific gom tests, but it's obvious when using a newer glib. It will assert() when running the existing tests under the new glib, without the fixes. Fixed in gom-0.4-1.el8 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 (gom bug fix and enhancement 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/RHBA-2020:4631 |