Closed mthaddon closed 3 weeks ago
Thanks for the issue @mthaddon.
In the latest version of paas-app-charmer, the charm can block on non optional integrations.
That is, if the postgresql relation in charmcraft.yaml
is not optional (optional: false
or not set), the charm will not try to run the migration where there in no integration with postegresq.
Closing this issue because:
Bug Description
Currently we try to run the schema update before the database is ready. We do it on any call of restart, so it fails a bunch of times before succeeding. Also, the message is misleading, we report to the end user (via unit status:
But this isn't true, it's not only on the next update status hook that this happens.
To Reproduce
repo-policy-compliance
is a flask application built with paas-app-charmerEnvironment
Microk8s 1.28.7, Juju 3.1.8
Relevant log output
Additional context
No response