http://bugzilla.suse.com/show_bug.cgi?id=960669
http://bugzilla.suse.com/show_bug.cgi?id=960669#c33
--- Comment #33 from Franck Bui
That's not what the openqa test showed. If it was rerenamed back to eth0, then the openqa test would not have failed. Something seems wrong with your system.
Initially this bug was about an upgrade from 13.2 to TW. In the case of 13.2, /etc/udev/rules.d/70-persistent-net.rules is just missing since as you already know, 75-persistent-net-rules-generator is boggus. And if the rule is missing, well no renaming happens obviously. However if you add manually a persistent rule in /etc/udev/rules.d in order to make sure that the virtio net interface is named "eth0" then it will work just fine. For some reasons the persistent net rules generator had been fixed on SLE12-SP1/Leap, and that the reason why the behavior is different and the reason why adding it in the initramfs makes difference. And here is what is generated by the generator: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:12:34:56", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" Please note the KERNEL=="eth*" condition. Right after the system switched to the final rootfs, the interface is named "ens3" (since 70-persistent-net.rules is not included). When udev is started (again), it reads 70-persistent-net.rules but the rule doesn't apply since the above condition is not met. So if you remove this condition, the renaming will work as expected even if systemd already renamed it "ens3" from within the initramfs. Now I have another question: why 80-net-setup-link.rules is included in the initramfs ? It's the rule which enables the predictable naming scheme done by udev for eth0, if I'm understanding correctly: if it's removed then the NIC name will be "eth0" as usual and the generated rule (if present) will work as expected. -- You are receiving this mail because: You are on the CC list for the bug.