Comment 7 for bug 1996794
Revision history for this message
| Felipe Reyes (freyes) wrote Re: juju deploy machine charm with --force fails with "ERROR no releases found for channel" | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
> The problem is related to "latest/edge" vs "edge" and the data we receive from charmhub.
it's worth to mention that for the case of mysql-innodb-
```
juju deploy --series kinetic --channel edge ch:mysql-
juju deploy --series kinetic --channel latest/edge ch:mysql-
```
The former should use `8.0/edge`, the default's track, which is fed by the git branch "stable/jammy", while `latest/edge` is fed by builds using the git branch "master".
> Looks like there is an issue with the resources for the charm related to the old bug (fixed?) where charms with resources needed resources to be specified when releasing to a track, even if they were no updated.
Revision 30 effectively is published without resources associated.
8.0 ubuntu 20.04 (amd64) stable be2f3d1 30 -
ubuntu 20.04 (arm64) stable be2f3d1 30 -
ubuntu 20.04 (ppc64el) stable be2f3d1 30 -
ubuntu 20.04 (s390x) stable be2f3d1 30 -
ubuntu 22.04 (amd64) stable be2f3d1 30 -
ubuntu 22.04 (arm64) stable be2f3d1 30 -
ubuntu 22.04 (ppc64el) stable be2f3d1 30 -
ubuntu 22.04 (s390x) stable be2f3d1 30 -