Closed baycarbone closed 2 months ago
Hi, @baycarbone, looks like the charm is depending on jinja being provided as a deep dependency. We should be able to add it as a direct dependency of the charm to solve this.
Latest 14/edge
(revisions 435 & 436) should have their own jinja2 installed.
Steps to reproduce
Expected behavior
Installation succeeds and status in juju is all green. If a dependency is missing I would expect the charm to install it.
Actual behavior
Installation fails and juju shows the postgres unit in error state. From the juju logs it seems the charms expects the jinja module to be available but on the desktop image the python3-jinja2 package is not installed by default. After installing the package manually, the installation proceeds successfuly.
Versions
Operating system: Ubuntu 22.04.4 LTS
Juju CLI: 3.4.4-genericlinux-amd64
Juju agent: 3.4.4
Charm revision: 429
Log output
Juju debug log:
Additional context
The same test on an AWS VMs succeeds using image:
ubuntu/images/hvm-ssd/ubuntu-jammy-22.04-amd64-server-*
as it comes with python3-jinja2 installed by default.