[Bionic]udev stop notifying when network interface added

Bug #1774132 reported by Talat Batheesh
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Undecided
Unassigned

Bug Description

Expected:

After a network driver restart, the network interfaces are deleted and added again, the udev should notify that new interface was added. then the interface service should be started accordingly.

Actual:
Udev doesn't notify about that new interface is added and the interface service doesn't start.

More details:

We see this issue when using Mellanox OFED package.
Mellanox OFED add a service per network device and add udev rule to start this service when the interface added.
After driver restart ("/etc/init.d/openibd restart") the network devices doesn't loaded, since udev doesn't notify.

The system should run from udev rules, since once the driver creates an interface, there should be a udev event saying a new interface is added, then this script will be ran by udev (the OS).

" /bin/systemctl --no-block start <email address hidden> "

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Could you please collect the udevadm monitor logs, across the openibd restart, both with a previously known working release (e.g. xenial?!) and bionic?

Together with dmesg output, to see what kernel was doing at the same time.

Revision history for this message
Talat Batheesh (talat-b87) wrote :
Revision history for this message
Talat Batheesh (talat-b87) wrote :
Revision history for this message
Talat Batheesh (talat-b87) wrote :

Thank you Dima,
Added requested files.

yours,
Talat

Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments