Environment destroy can miss manual machines
Bug #1475212 reported by
Jesse Meek
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-ci-tools |
Fix Released
|
Critical
|
Christopher Lee | ||
juju-core |
Invalid
|
Undecided
|
Unassigned | ||
1.25 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
We need to be able to assert the absence of these as part of the destroy txn in state/environ.go, but in order to do this manual machines need to add refcounts to their environments - such that they can be handled in a similar fashion to hosted environments.
tags: | added: manual-provider |
tags: | added: destroy-environment |
tags: | added: tech-debt |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju-core: | |
milestone: | 1.25.0 → 1.25.1 |
summary: |
- Environment destroy can miss manual machines and persistent - volumes + Environment destroy can miss manual machines |
description: | updated |
Changed in juju-core: | |
milestone: | 1.25.1 → none |
Changed in juju-core: | |
milestone: | none → 1.26-alpha2 |
Changed in juju-core: | |
milestone: | 1.26-alpha2 → 1.26.0 |
Changed in juju-core: | |
milestone: | 1.26.0 → none |
tags: | added: manual-story |
Changed in juju-core: | |
milestone: | none → 2.0.0 |
Changed in juju-core: | |
milestone: | 2.0-beta15 → 2.0-beta16 |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → In Progress |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta16 → none |
milestone: | none → 2.0-beta16 |
tags: | added: blocker |
Changed in juju: | |
importance: | High → Critical |
Changed in juju: | |
assignee: | Andrew Wilkins (axwalk) → Tim Penhey (thumper) |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.0-beta16 → 2.0-beta17 |
tags: | removed: blocker |
Changed in juju-core: | |
status: | New → Invalid |
no longer affects: | juju |
To post a comment you must log in.
I think we'll change storage so that it doesn't need to be handled here. Persistent storage will be destroyed via the storage provisioner as per usual. There was a gap that has just been filled that meant persistent storage would be leaked by destroy-env; this is no longer true, so we can relax the rules of env destruction.