2.9 juju deploy not finding default channel correctly at deploy
Bug #2020218 reported by
Heather Lanigan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
High
|
Unassigned | ||
Bug Description
This is specific to 2.9 and does not appear in juju 3.3
$ juju deploy mysql
ERROR selecting releases: charm or bundle not found for channel "", platform "amd64"
available releases are:
channel "8.0/stable": available series are: jammy
channel "8.0/candidate": available series are: jammy
channel "8.0/beta": available series are: jammy
channel "8.0/edge": available series are: jammy
However specifying a revision allows the default charm to be found
$ juju deploy mysql --series jammy
Located charm "mysql" in charm-hub, revision 151
Deploying "mysql" from charm-hub charm "mysql", revision 151 in channel 8.0/stable on jammy
Happens with `juju download` as well.
| Changed in juju: | |
| milestone: | 2.9.43 → 2.9.44 |
| Changed in juju: | |
| milestone: | 2.9.44 → 2.9.45 |
| Changed in juju: | |
| milestone: | 2.9.45 → 2.9.46 |
To post a comment you must log in.
