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

Charmed deployment stuck on postgres "awaiting for primary endpoint to be ready" #552

Closed
kbaccar-core opened this issue Jul 5, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@kbaccar-core
Copy link

Hello,
Im following the main documentation to run charmed magma. Everything went approximately as expected, except for the deployment of the charm with this command: juju deploy magma-orc8r --overlay overlay.yaml --trust --channel=latest
Apparently the postgres application is stuck on " awaiting for primary endpoint to be ready".

Environment

Charm version: 1.8
Postgres Version: 14/edge
Affected Component: Postgres
Deployment Environment: AWS (orc8r)

Sceeenshot

Juju Status:

magmacore1

Juju Postgrs log:

magmacore2
@kbaccar-core kbaccar-core added the bug Something isn't working label Jul 5, 2024
Copy link
Contributor

github-actions bot commented Jul 5, 2024

@dragomirp
Copy link
Contributor

Hi, @kbaccar-core, IIRC there was an incompatibility between the charm and Juju 3.5.0. Can you try redeploying it on Juju 3.5.1 or Juju 3.4?

@taurus-forever
Copy link
Contributor

I am resolving this issue, as the modern charm revisions clearly insist/assumes in Juju 3.5.1+.

Also we have updated the list of supported Juju versions with the patch set level precision: https://charmhub.io/postgresql-k8s/docs/r-system-requirements (we will continue the work here to represent it better).

Dear @kbaccar-core Feel free to reopen this issue IF it is still reproducible on your side for modern/fixed Juju versions. Tnx!

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

3 participants