network-interface-container.conf should fire for openvz
Bug #1294155 reported by
Daniel Speichert
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ifupdown (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
network-
script
case "$CONTAINER" in
initctl emit --no-wait net-device-added INTERFACE=lo || true
;;
esac
end script
originally, it is: "lxc|lxc-libvirt)" (without openvz).
Without that change, loopback interface never goes up on openvz interface.
Tested with trusty-
| description: | updated |
| Changed in ifupdown (Ubuntu): | |
| status: | New → Fix Committed |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in ifupdown (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package ifupdown - 0.7.47.2ubuntu2
---------------
ifupdown (0.7.47.2ubuntu2) trusty; urgency=medium
[ Stéphane Graber ]
* Allow setting the MTU and HWADDR on manual interfaces. (LP: #1294807)
* The above change also means that manual interfaces will now be
brought up and down (ias many users expected until now).
* Disable link.defn as it's not covering all the cases supported by
the vlan and bridge hooks and so causes more harm than good at this
point. (LP: #1295304)
* Also enable network-
* Update networking.init to exit 1 on reload when on an upstart system.
* Pass --force to ifdown in network-interface to silence errors on
non-existing interfaces. (LP: #1295620)
[ Dimitri John Ledkov ]
* Prevent the ability to stop or restart networking service
interactively. As that is not supported. Networking job is only stopped
during shutdown sequence. (LP: #1072518)
-- Stephane Graber <email address hidden> Wed, 19 Mar 2014 18:04:49 -0400