Failing upgrade-charm of a kubernetes charm due to series mismatch

[Adam Dyess]

juju client version = 2.9.33-ubuntu-amd64
controller version = 2.9.33

A charm whose
metadata is https://paste.ubuntu.com/p/SHdmZbFZGk/
manifest is https://paste.ubuntu.com/p/xx695vGz8S/

fails to perform a local upgrade of a previously installed charm

~/git/charmed-kubernetes/metallb-operator/charms/metallb-speaker main*
❯ juju upgrade-charm metallb-speaker --path=./metallb-speaker_ubuntu-20.04-amd64_ubuntu-22.04-amd64.charm
ERROR series "focal" not supported by charm, supported series are: kubernetes

Build charm from here:
https://github.com/charmed-kubernetes/metallb-operator/tree/main/charms/metallb-speaker

Steps to reproduce:
* start with a kubernetes cluster (microk8s should work but disabling RBAC makes it easier)
* deploy from charmhub with `juju deploy metallb-speaker`
* wait for stable
* perform juju upgrade-charm metallb-speakder --path=<localtion of built charm>
* profit

[Juan M. Tirado (tiradojm)]

Confirmed in 2.9.33 and 3.0-rc1. This could be related with https://bugs.launchpad.net/juju/+bug/1983581

[John A Meinel (jameinel)]

So I think the issue here is that a v1 charm (using pod-spec-set) really does need `series: kubernetes` for it to operate correctly.
I wonder if we are taking the old style and then overriding its series once it is deployed back to say "focal" which would be true for a metadata v2 charm.

[Maksim Beliaev (beliaev-maksim)]

is there any workaround for the problem?

[Heather Lanigan (hmlanigan)]

Attempting to reproduce with juju 2.9.42.

$ juju deploy metallb-speaker
Located charm "metallb-speaker" in charm-hub, revision 36
WARNING deploying podspec charm "metallb-speaker": podspec charms are deprecated. Support for them will be removed soon.
Deploying "metallb-speaker" from charm-hub charm "metallb-speaker", revision 36 in channel stable on ubuntu@22.04/stable

Looking for an OCI image to deploy the local charm with.

[Heather Lanigan (hmlanigan)]

Looks like there is a problem in the refresh code. Deploying the same local charm that fails the refresh works

$ juju refresh metallb-speaker --path ./metallb-speaker_ubuntu-20.04-amd64-arm-arm64-ppc64le-s390x_ubuntu-22.04-amd64-arm-arm64-ppc64le-s390x.charm
ERROR series "jammy" not supported by charm, the charm supported series are: kubernetes

$ juju deploy ./metallb-speaker_ubuntu-20.04-amd64-arm-arm64-ppc64le-s390x_ubuntu-22.04-amd64-arm-arm64-ppc64le-s390x.charm --resource metallb-speaker-image=rocks.canonical.com/cdk/metallb/speaker:v0.12 addy
Located local charm "metallb-speaker", revision 1
WARNING deploying podspec charm "metallb-speaker": podspec charms are deprecated. Support for them will be removed soon.
Deploying "addy" from local charm "metallb-speaker", revision 1 on ubuntu@20.04/stable

[Heather Lanigan (hmlanigan)]

Juju is also picking a different "series" for the same charm depending on whether it's deployed from a respository, or it's deployed as a local charm in this case.

[Heather Lanigan (hmlanigan)]

I have a draft PR up for this bug: https://github.com/juju/juju/pull/15582

There may be some rough edges with this change I want to find.