persist iptables rules / routes for addressable containers across host reboots

Bug #1442012 reported by Dimiter Naydenov
8
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/interfaces to have pre-up and post-down scripts that add the rules and routes, like we do for the containers' /etc/network/interfaces.

Revision history for this message
Dimiter Naydenov (dimitern) wrote :

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.

Curtis Hovey (sinzui)
no longer affects: juju-core/1.23
Revision history for this message
Dimiter Naydenov (dimitern) wrote :

We need to get this fixed for 1.23.1, as it will affect customers.

Revision history for this message
Dimiter Naydenov (dimitern) wrote :

It's fine I guess to re-target this for 1.23.2 if the fix for bug 1445063 need to go out immediately.

Curtis Hovey (sinzui)
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
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.