https://pulp.plan.io/https://pulp.plan.io/favicon.ico2021-10-18T10:26:59ZPulpPulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=765762021-10-18T10:26:59Zevgenievgeni+pulp@redhat.com
<ul></ul><p>This is correctly detected by the API in status:</p>
<pre>
"online_content_apps": [],
</pre> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=765772021-10-18T10:53:13Zevgenievgeni+pulp@redhat.com
<ul></ul><p>You'd think it's a dupe of <a href="https://pulp.plan.io/issues/9275" class="external">https://pulp.plan.io/issues/9275</a></p>
<p>But this is on python3-pulpcore-3.14.7-1.el7.noarch, which got the above backported in <a href="https://pulp.plan.io/issues/9282" class="external">https://pulp.plan.io/issues/9282</a></p> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=765782021-10-18T10:58:40Zevgenievgeni+pulp@redhat.com
<ul></ul><p>And certainly related to <a href="https://pulp.plan.io/issues/9276" class="external">https://pulp.plan.io/issues/9276</a>, no idea how you want to stack those (or dupe ;))</p> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=765972021-10-19T08:12:18Zevgenievgeni+pulp@redhat.com
<ul></ul><p>Just verified, this also happens with pulpcore 3.16 (running on Python 3.8.11, Django 3.2.8)</p> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=765982021-10-19T08:22:04Zevgenievgeni+pulp@redhat.com
<ul></ul><p>And no, the changes in <a href="https://github.com/pulp/pulpcore/commit/d0dbc4247df8ecd76794cd93ed3e645e26fcbc22" class="external">https://github.com/pulp/pulpcore/commit/d0dbc4247df8ecd76794cd93ed3e645e26fcbc22</a> don't do anything :/</p> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=765992021-10-19T08:31:12Zevgenievgeni+pulp@redhat.com
<ul></ul><p>The following patch makes the content app work for me again after a DB restart, but I think using _reset_db_connection is just papering over the actual issue.</p>
<pre>
commit 60a21b41da1acd4f0bd6fc1984d8b66773d1ff3c
Author: Evgeni Golov
Date: Tue Oct 19 09:16:29 2021 +0200
reset DB connection before trying to get status
diff --git pulpcore/content/__init__.py pulpcore/content/__init__.py
index 396db3a1c..623098d77 100644
--- pulpcore/content/__init__.py
+++ pulpcore/content/__init__.py
@@ -40,6 +40,7 @@ async def _heartbeat():
msg = i8ln_msg.format(name=name, interarrival=heartbeat_interval)
def get_status_blocking():
+ Handler._reset_db_connection()
return ContentAppStatus.objects.get_or_create(name=name)
while True:
</pre> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=766082021-10-19T14:44:46Zipanova@redhat.comipanova@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - DUPLICATE</i></li></ul><p>dup of <a href="https://pulp.plan.io/issues/9276" class="external">https://pulp.plan.io/issues/9276</a></p> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=766092021-10-19T14:45:36Zmdellweg
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-1 status-11 priority-7 priority-high2 closed" href="/issues/9276">Issue #9276</a>: Content app can have unusable/closed db connections in pulpcore 3.15/3.16</i> added</li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768022021-10-25T20:27:45Zttereshcttereshc@redhat.com
<ul><li><strong>Status</strong> changed from <i>CLOSED - DUPLICATE</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>dkliban@redhat.com</i></li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Urgent</i></li></ul><p>Reopening the issue to track changes needed for 3.14.z.
Content app changed significantly between 3.15+ and 3.14, the solution for 3.15+ is different than the one needed for 3.14.z.</p> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768032021-10-25T20:28:14Zttereshcttereshc@redhat.com
<ul><li><strong>Is duplicate of</strong> deleted (<i><a class="issue tracker-1 status-11 priority-7 priority-high2 closed" href="/issues/9276">Issue #9276</a>: Content app can have unusable/closed db connections in pulpcore 3.15/3.16</i>)</li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768062021-10-25T20:28:22Zttereshcttereshc@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-11 priority-7 priority-high2 closed" href="/issues/9276">Issue #9276</a>: Content app can have unusable/closed db connections in pulpcore 3.15/3.16</i> added</li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768082021-10-25T20:29:04Zttereshcttereshc@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 108</i></li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768092021-10-25T20:30:27Zttereshcttereshc@redhat.com
<ul><li><strong>Subject</strong> changed from <i>content app doesn't survive PostgreSQL disconnect</i> to <i>content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7</i></li><li><strong>Sprint</strong> deleted (<del><i>Sprint 108</i></del>)</li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768102021-10-25T20:30:56Zttereshcttereshc@redhat.com
<ul><li><strong>Sprint</strong> set to <i>Sprint 108</i></li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768122021-10-25T20:32:00Zttereshcttereshc@redhat.com
<ul><li><strong>Tags</strong> <i>Katello</i> added</li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768642021-10-26T14:45:06Zdkliban@redhat.com
<ul><li><strong>Triaged</strong> changed from <i>No</i> to <i>Yes</i></li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=768952021-10-27T18:56:01Zpulpbot
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p>PR: <a href="https://github.com/pulp/pulpcore/pull/1701" class="external">https://github.com/pulp/pulpcore/pull/1701</a></p> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=770512021-11-04T21:23:09Zrchan
<ul><li><strong>Sprint</strong> changed from <i>Sprint 108</i> to <i>Sprint 109</i></li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=770542021-11-05T13:41:27Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li></ul><p>Applied in changeset <a class="changeset" title="Improves tolerance of db connection failures in pulpcore-content This patch moves Handler._reset..." href="https://pulp.plan.io/projects/pulp/repository/pulpcore/revisions/56f5e38164f04d181860d914735e3cf0ef3f5b6a">pulpcore|56f5e38164f04d181860d914735e3cf0ef3f5b6a</a>.</p> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=770602021-11-05T17:02:59Zpulpbot
<ul><li><strong>Sprint/Milestone</strong> set to <i>3.14.9</i></li></ul> Pulp - Issue #9515: content app doesn't survive PostgreSQL disconnect in pulpcore 3.14.7https://pulp.plan.io/issues/9515?journal_id=770622021-11-05T17:25:54Zpulpbot
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul>