Closed/removed track still shows up in charmhub, juju, but not charmcraft status
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
Undecided
|
Unassigned | ||
Snap Store Server |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Context/background:
* charmcraft 1.7.1 and 1.5
* juju 2.9.31
* charm: mysql-innodb-
Originally, there was a 8.0.19 track; a 8.0 track was added, and the 8.0.19 track was requested to be 'removed'. The 8.0 track is the default track.
However, juju and charmhub.io both show the 8.0.19 track; charmcraft does not.
The "https:/
juju info mysql-innodb-
name: mysql-innodb-
charm-id: i5HWuKoEat09854
summary: MySQL InnoDB Cluster
publisher: OpenStack Charmers
supports: focal, jammy
tags: cloud, databases
subordinate: false
store-url: https:/
description: |
MySQL InnoDB Cluster Charm deploys and manages the lifecycle of a
MySQL InnoDB Cluster.
relations:
provides:
db-monitor: mysql-monitor
db-router: mysql-router
shared-db: mysql-shared
requires:
certificates: tls-certificates
channels: |
8.0/stable: be2f3d1 2022-06-13 (26) 14MB
8.0/candidate: ↑
8.0/beta: ↑
8.0/edge: ↑
latest/stable: 15 2022-02-09 (15) 13MB
latest/candidate: ↑
latest/beta: ↑
latest/edge: 773bcae 2022-06-01 (27) 14MB
8.0.19/stable: be2f3d1 2022-05-05 (24) 14MB
8.0.19/candidate: be2f3d1 2022-04-28 (24) 14MB
8.0.19/beta: ↑
8.0.19/edge: be2f3d1 2022-04-27 (24) 14MB
And "charmcraft status mysql-innodb-
Track Base Channel Version Revision Resources
latest ubuntu 19.10 (all) stable 3 3 mysql-shell (r0)
ubuntu 20.04 (all) stable 15 15 mysql-shell (r0)
ubuntu 20.04 (amd64) stable - - -
ubuntu 20.04 (arm64) stable - - -
ubuntu 20.04 (ppc64el) stable - - -
ubuntu 20.04 (s390x) stable - - -
ubuntu 20.10 (all) stable 15 15 mysql-shell (r0)
ubuntu 21.04 (all) stable 15 15 mysql-shell (r0)
ubuntu 21.10 (all) stable 15 15 mysql-shell (r0)
ubuntu 22.04 (amd64) stable - - -
ubuntu 22.04 (arm64) stable - - -
ubuntu 22.04 (ppc64el) stable - - -
ubuntu 22.04 (s390x) stable - - -
5.7 - stable - - -
8.0 ubuntu 20.04 (amd64) stable be2f3d1 26 -
ubuntu 20.04 (arm64) stable be2f3d1 26 -
ubuntu 20.04 (ppc64el) stable be2f3d1 26 -
ubuntu 20.04 (s390x) stable be2f3d1 26 -
ubuntu 22.04 (amd64) stable be2f3d1 26 -
ubuntu 22.04 (arm64) stable be2f3d1 26 -
ubuntu 22.04 (ppc64el) stable be2f3d1 26 -
ubuntu 22.04 (s390x) stable be2f3d1 26 -
When charmcraft tries to close a risk on the 8.0.19 track:
charmcraft close mysql-innodb-
Store operation failed:
- None: Invalid track: 8.0.19
Full execution log: '/home/
2022-06-15 12:05:56.034 Starting charmcraft version 1.7.1
2022-06-15 12:05:56.034 Raw pre-parsed sysargs: args={'help': False, 'verbose': False, 'quiet': False, 'trace': False, 'project_dir': None} filtered=['close', 'mysql-
2022-06-15 12:05:56.034 General parsed sysargs: command='close' args=['
2022-06-15 12:05:56.034 Couldn't find config file '/home/
2022-06-15 12:05:56.035 Command parsed sysargs: Namespace(
2022-06-15 12:05:56.035 System details: OSPlatform(
2022-06-15 12:05:56.110 Retrieving credentials for 'charmcraft' on 'api.charmhub.io' from keyring 'SecretService Keyring'.
2022-06-15 12:05:56.145 HTTP 'POST' for 'https:/
2022-06-15 12:05:56.294 Store operation failed:
- None: Invalid track: 8.0.19
2022-06-15 12:05:56.294 Traceback (most recent call last):
2022-06-15 12:05:56.294 File "/snap/
2022-06-15 12:05:56.294 return method(self, *args, **kwargs)
2022-06-15 12:05:56.294 File "/snap/
2022-06-15 12:05:56.294 self._client.
2022-06-15 12:05:56.294 File "/snap/
2022-06-15 12:05:56.294 response = super()
2022-06-15 12:05:56.294 File "/snap/
2022-06-15 12:05:56.294 return self.http_
2022-06-15 12:05:56.294 File "/snap/
2022-06-15 12:05:56.294 raise errors.
2022-06-15 12:05:56.294 craft_store.
2022-06-15 12:05:56.294 - None: Invalid track: 8.0.19
2022-06-15 12:05:56.294 Full execution log: '/home/
Juju downloading various versions:
$ juju download mysql-innodb-
Fetching charm "mysql-
Install the "mysql-
juju deploy ./mysql-
$ juju download mysql-innodb-
Fetching charm "mysql-
Install the "mysql-
juju deploy ./mysql-
So the default track is 8.0/stable.
juju download mysql-innodb-
Fetching charm "mysql-
Install the "mysql-
juju deploy ./mysql-
So juju can download the 8.0.19 charm.
The issue:
juju and charmhub.io can 'see' and access the 8.0.19 track. charmcraft can't, and also won't allow the track/risk to be manipulated/closed. There's an inconsistency amongst the applications that access the charmhub.
Also raised on charmcraft: https:/
description: | updated |
Juju fully depends on charmhub.io to deploy charms. There are no special tracks for Juju to access removed data/charms. This is probably and ongoing issue with Charmhub.io rather than Juju itself.