force remove unit with subordinates warnings
Bug #1946058 reported by
Ian Booth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Observed in the logs of a deployment where remove-unit --force was used (not for any particular reason, --force was used because the user didn't want to wait for things to terminate cleanly).
machine-0: 09:56:29 WARNING juju.state cleanup failed in model cde23b50-
The above error is logged many times.
If the end result is a forced removal even with subordinates, there's not really a reason to warn the user about anything. It seems more like DEBUG would be suitable.
Changed in juju: | |
milestone: | 2.9.16 → 2.9.17 |
summary: |
- force remove unit fails with subordinates + force remove unit with subordinates warnings |
Changed in juju: | |
milestone: | 2.9.17 → 2.9.18 |
Changed in juju: | |
milestone: | 2.9.18 → 2.9.19 |
Changed in juju: | |
milestone: | 2.9.19 → 2.9.20 |
Changed in juju: | |
milestone: | 2.9.20 → 2.9.21 |
Changed in juju: | |
milestone: | 2.9.21 → 2.9.22 |
Changed in juju: | |
milestone: | 2.9.22 → 2.9.23 |
Changed in juju: | |
milestone: | 2.9.23 → 2.9.24 |
Changed in juju: | |
milestone: | 2.9.24 → 2.9.25 |
Changed in juju: | |
milestone: | 2.9.25 → 2.9.26 |
Changed in juju: | |
milestone: | 2.9.26 → 2.9.27 |
Changed in juju: | |
milestone: | 2.9.27 → 2.9.28 |
Changed in juju: | |
milestone: | 2.9.28 → 2.9.29 |
Changed in juju: | |
milestone: | 2.9.29 → 2.9.30 |
Changed in juju: | |
milestone: | 2.9.30 → 2.9-next |
tags: | added: teardown |
Changed in juju: | |
milestone: | 2.9-next → none |
To post a comment you must log in.
This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.