Comment 11 for bug 1996794

Some of the mysql-innodb-cluster data has changed since I responded in #5. There is now a default channel. So "edge" no longer should get "latest/edge", but instead "8.0/edge", which is a closed channel, afaik.

$ juju info mysql-innodb-cluster
name: mysql-innodb-cluster
publisher: OpenStack Charmers
summary: MySQL InnoDB Cluster
description: |
  MySQL InnoDB Cluster Charm deploys and manages the lifecycle of a
  MySQL InnoDB Cluster.
store-url: https://charmhub.io/mysql-innodb-cluster
charm-id: i5HWuKoEat09854Sz0qXHOjmr4wwHLfP
supports: focal, jammy
tags: cloud, databases
subordinate: false
relations:
  provides:
    db-monitor: mysql-monitor
    db-router: mysql-router
    shared-db: mysql-shared
  requires:
    certificates: tls-certificates
channels: |
  8.0/stable: be2f3d1 2022-11-22 (30) 15MB amd64, arm64, ppc64el, s390x focal, jammy
  8.0/candidate: ↑
  8.0/beta: ↑
  8.0/edge: ↑
  latest/stable: 15 2022-02-09 (15) 13MB amd64, arm64, armhf, i386, ppc64el, s390x focal, groovy, hirsute, impish
  latest/candidate: ↑
  latest/beta: ↑
  latest/edge: 95cc985 2022-11-28 (37) 15MB amd64, arm64, ppc64el, s390x jammy

This is now a different bug than originally reported, though the same user experience.

$ sjuju deploy --channel edge --series kinetic --force ch:mysql-innodb-cluster
Located charm "mysql-innodb-cluster" in charm-hub, revision 30
ERROR listing resources for charm "ch:amd64/kinetic/mysql-innodb-cluster-30": No revision was found in the Store.

Juju is looking for resources in the 8.0/stable channel, but appears to ignore force.