TL;DR: is it not possible to deploy closed channels using Juju 3.1.6 today. Resolved?
re: > And mysql-router itself doesn't even have resources (that I can find)
The ticket is about K8s charms: "unable to fetch OCI image resources", but you were checking mysql-router VM.
Anyway, today, using Juju 3.1.6 I cannot reproduce the initial issue at all
(e.g. mysql-k8s latest/* are closed):
> > juju deploy mysql-k8s --channel latest/edge --trust
> ERROR selecting releases: charm or bundle not found for channel "latest/edge", platform "amd64"
> available releases are:
> channel "8.0/edge": available series are: jammy
> channel "8.0/stable": available series are: jammy
> channel "8.0/candidate": available series are: jammy
> channel "8.0/beta": available series are: jammy
I believe something has changed on Juju/Charmhub level.
Hi Jon, thank you for trying to trace this down.
TL;DR: is it not possible to deploy closed channels using Juju 3.1.6 today. Resolved?
re: > And mysql-router itself doesn't even have resources (that I can find)
The ticket is about K8s charms: "unable to fetch OCI image resources", but you were checking mysql-router VM.
Anyway, today, using Juju 3.1.6 I cannot reproduce the initial issue at all
(e.g. mysql-k8s latest/* are closed):
> > juju deploy mysql-k8s --channel latest/edge --trust
> ERROR selecting releases: charm or bundle not found for channel "latest/edge", platform "amd64"
> available releases are:
> channel "8.0/edge": available series are: jammy
> channel "8.0/stable": available series are: jammy
> channel "8.0/candidate": available series are: jammy
> channel "8.0/beta": available series are: jammy
I believe something has changed on Juju/Charmhub level.