Closed marceloneppel closed 1 month ago
From https://chat.charmhub.io/charmhub/pl/yg6asxao6f8hpn93xpq83efrte Marcelo wrote:
I created a new revision for the PostgreSQL charm on the 14/edge/test channel. It should have the fix to start PostgreSQL (and avoid it being stuck with the awaiting for cluster to start message). I couldn't reproduce the Juju secrets issue that you showed me in the logs, but now the PostgreSQL charm should be able to start.
....
If that revision works, I should create a pull request to later publish the revision correctly to the 14/edge channel.
We are waiting for the fix confirmation to merge in edge...
@marceloneppel what is our plan here?
We'll need some help from Alex Kilroy to bootstrap the environment again. He was busy, so that we couldn't progress in this task.
Hi @ale8k , is it still reproducible on JAAS (with 14/stable or 14/candidate we are preparing for stable release now)? If so, can you help us with env to reproduce and troubleshoot there? Tnx!
Dear @ale8k are there any place we can reproduce this issue (see my comment above)? Tnx!
Hi @taurus-forever, I'm unsure on how to reproduce this... Perhaps @kian99 knows?
Ahh! This can be ignored, operator day has passed.
Resolving the ticket as no longer topical.
Data Team is still interested in JAAS deployment/testing and searching the environment to test and document it (separate story).
Tnx!
Steps to reproduce
Deploy PostgreSQL K8S from stable in
jimm.operatorinc.org
Expected behavior
Charm starts correctly.
Actual behavior
Charm stuck with the
awaiting for cluster to start
message.Versions
Juju CLI: 3.1.6
Juju agent: 3.1.5
Charm revision: 158
Pebble logs:
Additional context
Huge pages setting in the unit:
MM discussion