Container destruction doesn't mark IP addresses as Dead
Bug #1441206 reported by
Michael Foord
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
Critical
|
Michael Foord | ||
| 1.24 |
Fix Released
|
Critical
|
Michael Foord | ||
Bug Description
We have an addresser worker to remove dead IP addresses (that were statically allocated to a container on environments that support this). Machine destruction is not yet marking IP addresses as Dead, so addresses are still not being released.
| Changed in juju-core: | |
| milestone: | 1.23-beta4 → 1.23.0 |
Revision history for this message
| Michael Foord (mfoord) wrote | #1 |
| Changed in juju-core: | |
| milestone: | 1.23.0 → 1.24-alpha1 |
| tags: | added: destroy-unit network |
| Changed in juju-core: | |
| milestone: | 1.24-alpha1 → 1.24-beta1 |
| Changed in juju-core: | |
| importance: | High → Critical |
| Changed in juju-core: | |
| milestone: | 1.24-beta1 → 1.24-beta2 |
| Changed in juju-core: | |
| milestone: | 1.24-beta2 → 1.25.0 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reatargeted this so as not to block 1.23. A fix is imminent, but it's fine to go in a point release. IP addresses from destroyed containers will leak with the provider until this is fixed, but as soon as the fix is in place they will be reaped by the upgrade step (and destroying the host machine on ec2 will release allocated IPs automatically anyway).