OperationalError on charm deployment in k8s model

Bug #1902680 reported by Tom Haddon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-k8s-postgresql
Fix Released
Undecided
Unassigned

Bug Description

I'm using:

microk8s v1.19.3 1774 latest/edge canonical✓ classic

juju 2.9-rc2

I just tried the following in a new model:

juju deploy cs:~postgresql-charmers/postgresql-k8s postgresql
juju deploy cs:~mattermost-charmers/mattermost --config juju-external-hostname=foo.internal
juju add-relation mattermost postgresql:db
juju expose mattermost

I got the following https://paste.ubuntu.com/p/3W7dTQxXFj/

Note that I ran the deploy and relate commands pretty soon after each other, didn't wait for the charms to complete deployment.

Revision history for this message
Tom Haddon (mthaddon) wrote :

I tried again, this time waiting until the initial deployment of each charm had completed, but still got the same error. Checking the postgresql-0 pod directly I saw https://paste.ubuntu.com/p/jy3P8xv76x/

Revision history for this message
Stuart Bishop (stub) wrote :

I'll need to see the pod log or /var/log/postgresql/repmgr.log to see what failed. https://paste.ubuntu.com/p/jy3P8xv76x/ shows repmgr setup has hung. Possibly dns isn't working on this microk8s (perhaps the feature not enabled?)

Revision history for this message
Tom Haddon (mthaddon) wrote :

For the record, https://paste.ubuntu.com/p/Hxmk3hd2nk/.

Having chatted outside of this bug, sounds like there are some Juju 2.9 issues that you're working through currently.

Revision history for this message
Stuart Bishop (stub) wrote :
Changed in charm-k8s-postgresql:
status: New → Fix Released
Revision history for this message
Tom Haddon (mthaddon) wrote :

Yup, confirmed it works for me now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.