Juju 2.9.50 charm refresh fails with `ERROR unknown series for version: "24.04"`

[Aliaksandr Vasiuk]

Hi,

Charm refresh seems to be broken in juju 2.9.50.

Steps:
1. Bootstrap LXD juju 2.9.50 controller
2. juju add-model test-landscape
3. juju deploy landscape-server --channel="latest/stable" --revision=111 --series=jammy -n 1
4. juju refresh landscape-server
ERROR unknown series for version: "24.04"

I don't see anything special in the controller logs:
```
$ juju debug-log -m controller
machine-0: 12:49:03 INFO juju.apiserver.common setting password for "machine-0"
machine-0: 12:49:03 INFO juju.apiserver.common setting password for "unit-landscape-server-0"
machine-0: 12:49:03 INFO juju.apiserver.connection agent login: unit-landscape-server-0 for 449dd08b-c0b2-4ff7-8be3-17e5741dc87b
machine-0: 12:49:03 INFO juju.apiserver.common setting password for "unit-landscape-server-0"
machine-0: 12:49:03 INFO juju.apiserver.connection agent disconnected: unit-landscape-server-0 for 449dd08b-c0b2-4ff7-8be3-17e5741dc87b
machine-0: 12:49:03 INFO juju.apiserver.connection agent login: unit-landscape-server-0 for 449dd08b-c0b2-4ff7-8be3-17e5741dc87b
machine-0: 12:49:03 INFO juju.apiserver.common.networkingcommon machine "0": adding new device "lo" () with addresses [127.0.0.1/8 ::1/128]
machine-0: 12:49:03 INFO juju.apiserver.common.networkingcommon machine "0": adding new device "eth0" (00:16:3e:65:d8:8a) with addresses [10.60.78.62/24]
machine-0: 12:49:03 INFO juju.apiserver.common setting password for "unit-landscape-server-0"
machine-0: 12:49:03 INFO juju.worker.raft.raftforwarder claiming lease "449dd08b-c0b2-4ff7-8be3-17e5741dc87b:application-leadership#landscape-server#" for "landscape-server/0"
machine-0: 12:48:01 INFO juju.state new machine "0" has preferred addresses: private "", public ""
machine-0: 12:48:02 INFO juju.apiserver.common setting password for "machine-0"
machine-0: 12:48:02 INFO juju.cloudconfig Fetching agent: curl -sSf --connect-timeout 20 --noproxy "*" --insecure -o $bin/tools.tar.gz <[https://10.60.78.236:17070/model/449dd08b-c0b2-4ff7-8be3-17e5741dc87b/tools/2.9.50-ubuntu-amd64]>
machine-0: 12:48:02 INFO juju.container.lxd starting new container "juju-1dc87b-0" (image "ubuntu-22.04-server-cloudimg-amd64-lxd.tar.xz")
machine-0: 12:48:08 INFO juju.provider.lxd started instance "juju-1dc87b-0"
machine-0: 12:48:14 INFO juju.state machine "0" preferred private address changed from "" to "local-cloud:10.60.78.62@space:0"
machine-0: 12:48:14 INFO juju.state machine "0" preferred public address changed from "" to "local-cloud:10.60.78.62@space:0"
machine-0: 12:49:03 INFO juju.apiserver.connection agent login: machine-0 for 449dd08b-c0b2-4ff7-8be3-17e5741dc87b
machine-0: 12:49:03 INFO juju.apiserver.common setting password for "machine-0"
machine-0: 12:49:03 INFO juju.apiserver.connection agent disconnected: machine-0 for 449dd08b-c0b2-4ff7-8be3-17e5741dc87b
machine-0: 12:49:03 INFO juju.apiserver.connection agent login: machine-0 for 449dd08b-c0b2-4ff7-8be3-17e5741dc87b
```

My juju status and show-application
```
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
test-landscape localhost-localhost localhost/localhost 2.9.50 unsupported 12:53:24Z

App Version Status Scale Charm Channel Rev Exposed Message
landscape-server waiting 1 landscape-server latest/stable 111 no Waiting on relations: db, amqp, haproxy

Unit Workload Agent Machine Public address Ports Message
landscape-server/0* waiting idle 0 10.60.78.62 Waiting on relations: db, amqp, haproxy

Machine State Address Inst id Series AZ Message
0 started 10.60.78.62 juju-1dc87b-0 jammy Running

$ juju show-application landscape-server
landscape-server:
  charm: landscape-server
  series: jammy
  channel: latest/stable
  constraints:
    arch: amd64
  principal: true
  exposed: false
  remote: false
  life: alive
  endpoint-bindings:
    "": alpha
    amqp: alpha
    application-dashboard: alpha
    cos-agent: alpha
    data: alpha
    db: alpha
    hosted: alpha
    nrpe-external-master: alpha
    replicas: alpha
    website: alpha
```

Seems like juju for some reason tries to look for charm build on Noble, while it is only available in Jammy. But I want only Jammy in my case.

Expected behavior:
Juju refreshes charm to the lastest/stable on Jammy.

Best Regards,
Alex.

[Joseph Phillips (manadart)]

Assigned the Heather for comment. Is the issue here that revision has been supplied explicitly for the initial deployment?

I wonder if it works with --force-series.

[Haw Loeung (hloeung)]

`--force-series` doesn't work:

| $ juju upgrade-charm haproxy --force-series
| ERROR unknown series for version: "24.04"

[Ian Booth (wallyworld)]

I wonder if we just enable the "24.04" -> "noble" series name mapping in 2.9

[Heather Lanigan (hmlanigan)]

@wallyworld, that is one possibility, but I think there's a better way.

The problem is this bit of code:
https://github.com/juju/juju/blob/15bd5a491bbe9a2d1be96acf9417dd815b93a7a2/core/charm/repository/charmhub.go#L204-L207

What we should be doing instead is logging the error and continuing to be more resilient. As long as there is a single base that juju knows about and is a supported workload for that juju version. Juju can keep going.

The same bug is in 3.1 and 3.4. 3.5 does not have that same bit of logic.

I was thinking it was a bug I've seen where on 3.x, if the charm supported centos for example, juju would fail to deploy the charm even, if it also supported ubuntu 22.04. Not sure if that's still around. Haven't found the bug.

[Heather Lanigan (hmlanigan)]

This no longer occurs in the juju 2.9/edge channel. I believe we added noble to the list of series for tests?