persist iptables rules / routes for addressable containers across host reboots
Bug #1442012 reported by
Dimiter Naydenov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
James Tunnicliffe | ||
1.23 |
Fix Released
|
High
|
James Tunnicliffe | ||
1.24 |
Fix Released
|
High
|
James Tunnicliffe |
Bug Description
If an instance hosting addressable containers is rebooted, the iptables rules and static routes on the instance allowing access to the hosted containers are not created so the containers are not accessible. We need to make sure those rules and routes are created on every boot. One option is to modify the host's /etc/network/
no longer affects: | juju-core/1.23 |
Changed in juju-core: | |
milestone: | 1.24-alpha1 → 1.25.0 |
Changed in juju-core: | |
assignee: | nobody → James Tunnicliffe (dooferlad) |
Changed in juju-core: | |
status: | Triaged → In Progress |
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.
I'm not targeting this towards 1.23-beta4 as I don't want to block the release, but there's no 1.23-beta5 milestone yet.