Ubuntu
ifupdown package

/etc/udev/rules.d/85-ifupdown.rules is broken

Bug #136470 reported by Olaf Lüke
6
Affects Status Importance Assigned to Milestone
ifupdown (Ubuntu)
Incomplete
Undecided
Colin Watson

Bug Description

hotplug does work only one time becouse of a wrong position of the END label.

Revision history for this message
Olaf Lüke (borg) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

This seems entirely wrong; it will cause removing *any* kobject to run /sbin/ifdown. How did you arrive at this?

Changed in udev:
assignee: nobody → kamion
status: New → Incomplete
Revision history for this message
Pekka Pessi (ppessi) wrote :

The rules fails because DRIVERS is empty with ACTION=='remove' SUBSYSTEM=='net'. IOW udev never runs ifdown for the auto interface.

This also means that subsequent ifup fails because device is already listed in /var/run/network/ifstate.

The problem exists on feisty and gutsy. Dapper seems to have different rules that do not check for DRIVERS.

Patch attached: it runs ifup always with --force.

--Pekka

Revision history for this message
Pekka Pessi (ppessi) wrote :

See also <https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/130437>.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

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