Project

Profile

Help

Issue #9276

closed

Content app can have unusable/closed db connections in pulpcore 3.15/3.16

Added by ttereshc over 2 years ago. Updated about 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 109
Quarter:

Description

We've seen multiple times the django.db.utils.InterfaceError: connection already closed while using content app. See related issues.

A current workaround is to reset the db connection in multiple places in the code. This "solution" is likely not reliable if we are not resetting db connection before every db request.

This problem needs investigation to understand why Django doesn't take care of the db connections itself, and how to solve it properly.


Related issues

Related to Pulp - Issue #9275: Content app db connection can be closed while matching a distributionCLOSED - CURRENTRELEASEActions
Related to Container Support - Issue #8672: Registry handler loses database connectionCLOSED - CURRENTRELEASEipanova@redhat.comActions
Related to Pulp - Issue #6045: Pulp content app looses database connectionCLOSED - CURRENTRELEASEdaviddavisActions
Related to Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7CLOSED - CURRENTRELEASEdkliban@redhat.comActions
Copied to Pulp - Backport #9598: Backport #9276 to 3.16: Content app can have unusable/closed db connections in pulpcore 3.15/3.16CLOSED - CURRENTRELEASEdkliban@redhat.com

Actions

Also available in: Atom PDF