[Bug 1307429] Re: Existing allow-hotplug devices do not come up
Launchpad Bug Tracker
1307429 at bugs.launchpad.net
Thu May 1 23:29:20 UTC 2014
This bug was fixed in the package ifupdown - 0.7.48.1ubuntu1
---------------
ifupdown (0.7.48.1ubuntu1) utopic; urgency=medium
[ Stéphane Graber ]
* Merge from Debian. Remaining changes:
- Add transition code for moving /etc/init.d/networking from netbase
to ifupdown.
- On upgrade from 0.7.5ubuntu4, handle the fact that our unmodified
conffile may have a mismatch in the dpkg database and manually
shuffle the file around on upgrade. LP: #1217263.
- Always call dhclient with -1, Ubuntu carries a patch so that renewal
won't time out.
- 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-interface-container for OpenVZ. (LP: #1294155)
- 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)
- 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)
* Dropped NetworkManager.conf support, the NetworkManager
ifupdown:managed mode was never really supported and this causes quite a
massive delta on ifupdown's side.
If you do use that option at the moment, you will need to decide
between managing the interface with NetworkManager (removing it from
interfaces) or managing it with ifupdown (removing ifupdown:managed=true
and the interface from NM).
* Stopped removing /etc/default/networking. The file still won't be
used as the upstart jobs don't parse it but there wasn't a good reason
to carry this as a delta.
[ Benjamin Drung ]
* Fix network-interface upstart job to bring up allow-hotplug devices.
(LP: #1307429)
ifupdown (0.7.48.1) unstable; urgency=low
* Add --ignore-errors option.
* Handle errors correctly during interface deconfiguration.
ifupdown (0.7.48) unstable; urgency=low
* Ignore statuses on down, don't ignore them on up.
When configuring an interface, it's important for all commands
to succeed, so if anything fails, interface isn't marked as
configured. When deconfiguring it, however, we should do our
best we can to deconfigure it, so if something fails, that's
not the reason to stop trying.
Closes: #360806, #547587, #562962, #700811.
* Disable tests for DAD.
* Fix hurd static script with IPv6 support (Closes: #737084).
* Support preferred lifetime setting for tunnels (Closes: #735534).
* Provide an alternative iproute dependency to make backporting easier.
* Default to accept_ra=2 for inet6/auto (Closes: #739993, LP: #1260241)
-- Stephane Graber <stgraber at ubuntu.com> Thu, 01 May 2014 19:01:35 -0400
** Changed in: ifupdown (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1307429
Title:
Existing allow-hotplug devices do not come up
Status in “ifupdown” package in Ubuntu:
Fix Released
Status in “ifupdown” source package in Precise:
New
Status in “ifupdown” source package in Saucy:
New
Status in “ifupdown” source package in Trusty:
Triaged
Bug description:
Devices that are listed with allow-hotplug in /etc/network/interfaces
do not come up when they are hotplugged. "ip addr" shows that these
devices are down.
Steps to reproduce:
1) Install Ubuntu 12.04, 13.10, or 14.04 in a virtual machine (e.g. with libvirt) with one network device.
2) Modify /etc/network/interfaces to
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
allow-hotplug eth1
iface eth1 inet dhcp
allow-hotplug eth2
iface eth2 inet dhcp
3) Boot your virtual machine.
4) Type "ip addr" to show your network devices. It should show eth0 which should be up (but isn't)
5) Add/Hotplug one NIC to your virtual machine.
6) "ip addr" should show that eth1 is up too (but isn't)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1307429/+subscriptions
More information about the Ubuntu-sponsors
mailing list