| Summary: | [RFE] Upgrade to at least 2.5.2 to get rid of segfaults happening in openstack-glance | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Cyril Roelandt <cyril> | |
| Component: | python-psycopg2 | Assignee: | Pavel Raiskup <praiskup> | |
| Status: | CLOSED WONTFIX | QA Contact: | qe-baseos-daemons | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 7.4 | CC: | cyril, databases-maint, jscotka, pkajaba, pkubat | |
| Target Milestone: | rc | Keywords: | FutureFeature | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1387266 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-16 05:05:01 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: | ||
| Bug Depends On: | ||||
| Bug Blocks: | 1387266 | |||
|
Description
Cyril Roelandt
2016-10-18 14:25:00 UTC
Cyril, thanks for the report! > Description of problem: > Since 2.5.1 (the current version available in RHEL) a lot of bugs leading to > segfaults have been fixed. These bugs happen when we run our tests for the > openstack-glance package. Rebase in RHEL is not trivial/risky, and for rebase we need a better reasoning. Psycopg2 is in "base" channel and is a part of Python's API. What are the real issues you face here? Concrete segfaults? So we can decide whether it is OK to backport or we should rather rebase? Is this testsuite-only? Or does this block some product? > We would need to use at least 2.5.2, or the latest > version if possible. The release notes for python-psycopg2 clearly show a > number of fixed segfaults: http://initd.org/psycopg/docs/news.html . That html doesn't show what's not working for you. Thanks! Hello. So I tried reproducing the issue, but could not set up the same failing environment as the one I had in our CI. We worked around the issue by disabling the PostgreSQL tests. I think this can be closed if nobody else complains about these segfaults. Thanks for taking care of this bug! Thanks - I'm closing then. Still, feel free to reopen with more info. |