juju deploy jammy when focal requested

[Heather Lanigan]

`juju deploy postgresql --series focal` should fail today charm revision, 288, at the tip of the default channel, 1.4/stable only supports jammy. Instead a jammy only channel was deployed on focal.

This also reproduces in 3.1 and 3.2, but not 3.3.beta2 right now

$ juju deploy postgresql --series focal
Located charm "postgresql" in charm-hub, revision 288
Deploying "postgresql" from charm-hub charm "postgresql", revision 288 in channel 14/stable on focal

juju:PRIMARY> db.charms.find({"_id" : "97b73441-4d56-471c-80f0-c64d19e2ca9a:ch:amd64/focal/postgresql-288"},{"meta.series":1, "manifest":1}).pretty()
{
 "_id" : "97b73441-4d56-471c-80f0-c64d19e2ca9a:ch:amd64/focal/postgresql-288",
 "meta" : {
  "series" : [
   "jammy"
  ]
 },
 "manifest" : {
  "bases" : [
   {
    "name" : "ubuntu",
    "channel" : {
     "track" : "22.04",
     "risk" : "stable",
     "branch" : ""
    },
    "architectures" : [
     "amd64"
    ]
   }
  ]
 }
}

[John A Meinel (jameinel)]

I get this error when trying to use the 3.3 client:
$ juju --logging-config "#charmhub=TRACE" deploy postgresql --base ubuntu@20.04
ERROR base "ubuntu@20.04/stable" is not supported, supported bases are: ubuntu@22.04
ERROR failed to deploy charm "postgresql"

So it seems we are doing the right thing in 3.3, we just need to fix earlier revisions to refuse to deploy a charm that doesn't support the requested series.

[Heather Lanigan (hmlanigan)]

This was fixed in 2.9.46