http://bugzilla.suse.com/show_bug.cgi?id=960669
http://bugzilla.suse.com/show_bug.cgi?id=960669#c29
--- Comment #29 from Fabian Vogt
why do you fear breakage? TW doesn't use persistent names so the file in question doesn't exist unless it was an upgrade from e.g. leap.
Has this changed during some point in TW?
The change from persisent to predicable was in 13.1 already AFAICT, so very long ago.
I have a old Tumbleweed system here that uses "ens*".
Which is expected as that is a predictable name :-) That system doesn't have 70-persistent-net.rules then, right?
I don't know, I only have the config files for it (ifcfg-ens1).
Just to summarize, we are talking about upgrade problems here and the problems are different depending on base distro:
1. upgrade from leap: leap uses persistent names (eth0), just as SLE, so an upgrade to TW must honor 70-persistent-net.rules 2. upgrade from 13.2: 13.2 does use predicatable names but udev on 13.2 apparently didn't support predicable names for virtio devices. So in openQA all machines still used eth0.
1) will be immediately fixed when dracut includes 70-persistent-net.rules in initrd again.
2) requires an additional workaround in 13.2 to create 70-persistent-net.rules, we may do that in openQA or just don't test upgrades from 13.2 anymore :-)
I talked to trenn, the cause for the (chaotic) revert is bug 886669. Basically, 70-persistent-net.rules does not work correctly in the initrd due to various reasons and bugs. It also conflicts with dracut's network naming scheme (but that can be fixed). I'll only commit the removal of forced virtio-net in QEMU, that should fix it as well. -- You are receiving this mail because: You are on the CC list for the bug.