Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove workaround #386

Open
marceloneppel opened this issue Feb 2, 2024 · 3 comments
Open

Remove workaround #386

marceloneppel opened this issue Feb 2, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@marceloneppel
Copy link
Member

Remove the workaround for canonical/pebble#149.

@marceloneppel marceloneppel added the bug Something isn't working label Feb 2, 2024
Copy link
Contributor

github-actions bot commented Feb 2, 2024

@taurus-forever
Copy link
Contributor

@marceloneppel can you please point the workaround you are referring here. Tnx!

@marceloneppel
Copy link
Member Author

@marceloneppel can you please point the workaround you are referring here. Tnx!

@taurus-forever:

# Restart the Patroni process if it was killed (in that case, the PostgreSQL
# process is still running). This is needed until
# https://github.com/canonical/pebble/issues/149 is resolved.
if not self._patroni.member_started and self._patroni.is_database_running:
try:
container.restart(self._postgresql_service)
logger.info("restarted Patroni because it was not running")
except ChangeError:
logger.error("failed to restart Patroni after checking that it was not running")
return False
return True

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants