Deploy to existing machine: "base does not match" even when series supported
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
The setup is: I'm inside a model with a single machine "0" which is running ubuntu@22.04 / jammy. When I try deploy certain charms to this machine, this happens:
-------
$ juju deploy juju-dashboard d --to 0
Located charm "juju-dashboard" in charm-hub, revision 6
Deploying "d" from charm-hub charm "juju-dashboard", revision 6 in channel stable on ubuntu@20.04/stable
ERROR cannot add application "d": cannot deploy to machine 0: base does not match: unit has "ubuntu@20.04", machine has "ubuntu@22.04"
-------
However, the juju-dashboard charm supports jammy, so this deployment should work fine. It appears that it is asking Charmhub for the default series, trying to match this against the machine series, and failing when they don't match. Instead, we should read the machine series and request this series from Charmhub.
For now, a workaround is to specify --series:
juju deploy juju-dashboard d --to 0 --series jammy
-------
$ juju version --all
version: 3.0.1-ubuntu-amd64
git-commit: deb94d4cac9efe4
-------
Changed in juju: | |
milestone: | none → 3.0.1 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju: | |
milestone: | 3.0.1 → 3.0.2 |
Changed in juju: | |
milestone: | 3.0.2 → 3.0.3 |
Changed in juju: | |
milestone: | 3.0.3 → 3.0.4 |
Can we check this again?