[Bug]: model.deploy does not behave like juju command

[amandahla]

Description

Environment

juju 2.9.42
juju==3.0.4

Scenario

1. Channel latest/table and series focal (20.04) are available at PostgreSQL-K8S Charmhub

2. The command juju deploy postgresql-k8s --channel=latest/stable --series=focal deploys the charm postgresql-k8s as expected:
   juju deploy output:

Located charm "postgresql-k8s" in charm-hub, revision 20
Deploying "postgresql-k8s" from charm-hub charm "postgresql-k8s", revision 20 in channel latest/stable on focal

juju status output:

juju status
Model      Controller   Cloud/Region        Version  SLA          Timestamp
indico-18  github-pr-2  microk8s/localhost  2.9.42   unsupported  14:37:37-03:00

App             Version  Status   Scale  Charm           Channel        Rev  Address  Exposed  Message
postgresql-k8s           waiting      1  postgresql-k8s  latest/stable   20           no       agent initializing

Unit               Workload     Agent      Address  Ports  Message
postgresql-k8s/3*  maintenance  executing                  (install) installing charm software

3. But deploying it while running an integration test using ops_test.model.deploy("postgresql-k8s",series="focal", channel="latest/stable") throws an error:

juju.errors.JujuError: Series focal not supported for ch:postgresql-k8s. Only ['jammy']

Expected

Deploy the charm postgresql-k8s accordingly to parameters channel latest/stable and series focal.

Reference

https://discourse.charmhub.io/t/juju-operators-for-postgresql-and-mysql-are-now-stable/10223/4

Urgency

Annoying bug in our test suite

Python-libjuju version

3.0.4

Juju version

2.9.42

Reproduce / Test

ops_test.model.deploy("postgresql-k8s",series="focal", channel="latest/stable")

[juanmanuel-tirado]

Hi @amandahla you probably want to use juju==2.9.42.3 here which is the latest release tested with the 2.9.42 controller. The python-libjuju 3.0.x series is no longer going to be maintained. This means that the python-libjuju version must match the controller major for compatibility.

I think this will fix the issue. Please reopen is required.

[amandahla]

Hi @juanmanuel-tirado thanks. But I tried now with juju 2.9.42.3 and got a different error this time:
juju.errors.JujuError: resolving retry error: No revision was found in the Store.

ps.: I think I can't reopen this issue. Should I open a new one?

[juanmanuel-tirado]

Sorry, I think I tested this issue with the wrong branch.

We have a regression in the 2.9 branch. I can confirm this works in 3.1 and master branches.

We have to check what is going on there. We need a backport and a new release with the corresponding fix. I will put some priority on this.