juju download: ERROR "mysql-router" does not support series

Bug #1975510 reported by Felipe Reyes
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
High
Unassigned

Bug Description

When trying to download a charm compatible with impish, which according to "juju info" there are 2 that match the criteria (revisions 14 in cadidate and 15 in stable) the command fails indicating the charm doesn't support the series requested, although in the same error message says "impish" is a supported series.

the output of "charmcraft status mysql-router" can be found at https://pastebin.ubuntu.com/p/hSR8fpDQdt/ which contains a more comprehensive list of channels, bases, architectures and revisions.

[Test Case]

$ juju info --arch amd64 --series impish mysql-router
name: mysql-router
charm-id: CjjVf4bSJGT6rKjg7Qk3EZteCoEhKXHh
...
  latest/stable: 15 2022-02-09 (15) 13MB
  latest/candidate: 14 2021-10-19 (14) 13MB
  latest/beta: ↑
  latest/edge: ↑
...

$ juju download --arch amd64 --series impish mysql-router
ERROR "mysql-router" does not support series "impish" in channel "stable". Supported series are: eoan, focal, groovy, hirsute, impish.
$ juju download --channel latest/edge --arch amd64 --series impish mysql-router
ERROR "mysql-router" does not support series "impish" in channel "edge". Supported series are: eoan, focal, groovy, hirsute, impish, jammy.
$ juju download --channel latest/candidate --arch amd64 --series impish mysql-router
ERROR "mysql-router" does not support series "impish" in channel "candidate". Supported series are: eoan, focal, groovy, hirsute, impish.
$ juju download --channel latest/stable --arch amd64 --series impish mysql-router
ERROR "mysql-router" does not support series "impish" in channel "stable". Supported series are: eoan, focal, groovy, hirsute, impish.

Tags: charmhub
Revision history for this message
Felipe Reyes (freyes) wrote :

juju deploy finds revision 26, this should be because the '8.0' track is the default track for this charm.

$ juju deploy --force --series impish --channel latest/edge mysql-router
Located charm "mysql-router" in charm-hub, revision 26
Deploying "mysql-router" from charm-hub charm "mysql-router", revision 26 in channel 8.0/edge on impish

Revision history for this message
Ian Booth (wallyworld) wrote :

At the very least, info with --series should only display channels that have that series.

eg this worked

juju download --arch amd64 --series impish mysql-router --channel=8.0.19/edge

Changed in juju:
importance: Undecided → High
status: New → Triaged
milestone: none → 2.9-next
tags: added: charmhub
Revision history for this message
Heather Lanigan (hmlanigan) wrote (last edit ):

There may be a problem on the charmhub side as well.

`juju download mysql-router --series impish --channel latest/stable`

makes the equivalent call as:

curl -s https://api.snapcraft.io/v2/charms/refresh -H 'Content-type: application/json' -d '{"context":[],"actions":[{"action":"install","instance-key":"d1708d3b-3101-4df9-87c6-9aa46651fd5d","name":"mysql-router","channel":"stable","base":{"architecture":"amd64","name":"ubuntu","channel":"21.10"}}],"fields":["bases","config-yaml","download","id","license","metadata-yaml","name","publisher","resources","revision","summary","type","version"]}'

Which returns an error: "code":"revision-not-found","message":"No revision was found in the Store."

However the error data returned, which supplied supported bases, includes what was requested:
            {
              "base": {
                "architecture": "amd64",
                "channel": "21.10",
                "name": "ubuntu"
              },
              "channel": "stable"
            },

The juju error message is confusing agreed, but it's based on the result of the api call, which is returning unexpected data.

Filed a bug with charmhub: https://bugs.launchpad.net/snapstore-server/+bug/1977774

Ian Booth (wallyworld)
Changed in juju:
milestone: 2.9-next → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.