destroy model fails if there's a relation to offered application
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Ian Booth |
Bug Description
Found with test-cmr-
https:/
When run locally:
$ juju status
Model Controller Cloud/Region Version SLA Timestamp
other ctrl-2zk8h41a aws/us-east-1 2.9.23.1 unsupported 14:45:43Z
SAAS Status Store URL
mysql terminated ctrl-2zk8h41a admin/test-
App Version Status Scale Charm Store Channel Rev OS Message
wordpress active 1 wordpress charmstore stable 0 ubuntu
Unit Workload Agent Machine Public address Ports Message
wordpress/0* active idle 0 18.209.69.95 80/tcp
Machine State DNS Inst id Series AZ Message
0 started 18.209.69.95 i-0ef5700031291c278 bionic us-east-1b running
$ juju status -m test-cmr-
Model Controller Cloud/Region Version SLA Timestamp Notes
test-cmr-
App Version Status Scale Charm Store Channel Rev OS Message
mysql unknown 0 mysql charmhub stable 58 ubuntu
Offer Application Charm Rev Connected Endpoint Interface Role
mysql mysql mysql 58 1/1 db mysql provider
tags: |
added: regression removed: reg |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | 2.9.23 → 2.9.24 |
Changed in juju: | |
milestone: | 2.9.24 → 2.9.25 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
The root cause might not be cmr related (EDIT: I was wrong, see below). It looks like there's been a change in behaviour (probably not intentional) where if you remove the last unit of an application, the application (with 0 units) stays behind. This is what's preventing the model from being removed.
eg
juju bootstrap
juju deploy ubuntu
juju remove-unit ubuntu/0
juju status
shows app "ubuntu" with scale 0