Skip to content
This repository has been archived by the owner on Feb 14, 2024. It is now read-only.

mysql charm version in charm store still points revision 58 by default #33

Open
davecore82 opened this issue Dec 28, 2018 · 2 comments
Open

Comments

@davecore82
Copy link

Running juju deploy mysql still deploys mysql revision 58 (which tries to deploy to a zesty machine and fails with the error "no matching agent binaries available").

This seems to be because the charm store points to revision 58 by default, even though version 62 is available.

@davecore82
Copy link
Author

I see that revision 58 is still the stable channel and 62 is in candidate, beta and edge:

charm show mysql -c stable

[...]
Revision 58
Supported Series zesty, xenial, trusty
[...]
CHANNEL CURRENT
stable true

charm show mysql -c beta

[...]
Revision 62
Supported Series xenial, bionic, trusty
[...]
CHANNEL CURRENT
candidate true
beta true
edge true

@tai271828
Copy link

tai271828 commented Jul 30, 2020

For people who care about this issue, this discourse thread may help https://discourse.juju.is/t/whats-up-with-mysql/149/14

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants