Clark Boylan
f07e8dd438
It seems on CentOS 9 (maybe others?) instance boot with an eth0 interface that is renamed to something like ens3. When that renaming happens it seems to short circuit eth0 udev event handling so glean never sees an add event for eth0 (which wouldn't be correct anyway since it has been renamed). Then the ens3 event is a move event and our udev rule doesn't match that which means we never run glean for ens3 either. Fix this by handling add|move in the ACTION list of our udev rule for glean so that we run glean for ens3 when it has been moved. Change-Id: I5369afb425dcf17e7539a4dd000231830862802b
2 lines
125 B
Plaintext
2 lines
125 B
Plaintext
SUBSYSTEM=="net", ACTION=="add|move", ATTR{addr_assign_type}=="0", TAG+="systemd", ENV{SYSTEMD_WANTS}+="glean@$name.service"
|