Closed jack-w-shaw closed 2 months ago
Yeah this makes sense, let's also add an integration test that deploys a workload on noble, just to catch future regressions about that, because compatibility across versions will be relevant when the 4.0 comes, we don't wanna miss anything there.
Integration test added
/merge
/merge
Hey guys! is there any ETA for this patch to land ?
/merge
Hm, it looks like merging is still blocked?
@UtkarshBhatthere @sabaini Yeah we're currently working on fixing some trouble with the jenkins job, it should be fixed in a day or two, after that, we're good to go 👍
/merge
/merge
/merge
/merge
The pylibjuju client hardcodes a mapping between series codename and the base channel.
Noble was absent from this mapping, meaning pylibjuju doesn't know know to deploy to noble.
Add noble to this mapping.
After noble, we will only support deploying by base. Noble will be the last series added to this map
Fixes: https://github.com/juju/python-libjuju/issues/1062
QA Steps
Download a local charm
juju download ubuntu
, unzip, and amend themanifest,yaml
to support ubuntu@24.04Place the charm dir at
./ubuntu
You will see
Then:
All CI tests need to pass.