Project

General

Profile

Bug #33744

workaround for pulpcore-content PostgreSQL connection issue

Added by Evgeni Golov 3 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Foreman modules
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

when pulpcore-conent loses its database connection, it does not re-establish it properly, leading to a broken content app (see https://pulp.plan.io/issues/9276 for details)

as the installer does restart the database sometimes, we could notify the content app, so that at least in these cases it's also restarted and thus can reconnect

Associated revisions

Revision 440a8e05 (diff)
Added by Evgeni Golov 3 months ago

Fixes #33744 - notify the socket service when the DB changes

pulpcore-content fails to reconnect to the database,
so schedule a restart whenever the db changes
see https://pulp.plan.io/issues/9276 for details

History

#1 Updated by The Foreman Bot 3 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-pulpcore/pull/234 added

#2 Updated by Evgeni Golov 3 months ago

  • Status changed from Ready For Testing to Closed

#3 Updated by Ewoud Kohl van Wijngaarden 3 months ago

  • Triaged changed from No to Yes
  • Category set to Foreman modules
  • Fixed in Releases 3.1.0 added

Also available in: Atom PDF