`juju deploy --force --to X` should disable series checks

Bug #1996829 reported by Jordan Barrett
8
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Triaged
Medium
Nicolas Vinuesa

Bug Description

deploy --force should disable series checks, however the following is failing because "series does not match". This is on Juju 2.9-latest.

$ juju add-machine --series kinetic
created machine 1
$ juju deploy mysql-innodb-cluster --series jammy --channel latest/edge --to 1 --force
Located charm "mysql-innodb-cluster" in charm-hub, revision 36
Deploying "mysql-innodb-cluster" from charm-hub charm "mysql-innodb-cluster", revision 36 in channel latest/edge on jammy
ERROR cannot add application "mysql-innodb-cluster": cannot deploy to machine 1: series does not match

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.9.38
Changed in juju:
milestone: 2.9.38 → 2.9.39
Changed in juju:
assignee: nobody → Nicolas Vinuesa (nvinuesa)
Changed in juju:
status: Triaged → In Progress
Changed in juju:
milestone: 2.9.39 → 2.9.40
Changed in juju:
milestone: 2.9.40 → 2.9.41
Changed in juju:
milestone: 2.9.41 → 2.9.42
Changed in juju:
milestone: 2.9.42 → 2.9.43
Changed in juju:
status: In Progress → Triaged
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.