https://bugzilla.novell.com/show_bug.cgi?id=850732 https://bugzilla.novell.com/show_bug.cgi?id=850732#c Xiyuan Liu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |mt@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=850732 https://bugzilla.novell.com/show_bug.cgi?id=850732#c3 Marius Tomaschewski changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@suse.com --- Comment #3 from Marius Tomaschewski 2013-11-18 09:59:37 UTC --- (In reply to comment #2)

The /etc/udev/rules.d/70-persistent-net.rules should still exists after an upgrade and should be used... Reassign to udev maintainer.

Ahm... more correctly. It IMO shouldn't be rewritten from BUS to MAC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=850732 https://bugzilla.novell.com/show_bug.cgi?id=850732#c Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |f+novell@congenio.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=850732 https://bugzilla.novell.com/show_bug.cgi?id=850732#c6 --- Comment #6 from Robert Milasan 2013-11-18 10:39:44 UTC --- Well, then that has nothing to do with udev. If the rules where generated correctly it would work as expected. The best way is to use the mac address, that doesn't change at all (at least it shouldn't). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=850732 https://bugzilla.novell.com/show_bug.cgi?id=850732#c8 Uwe Meyer-Gruhl changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|f+novell@congenio.de | --- Comment #8 from Uwe Meyer-Gruhl 2013-11-18 11:49:30 UTC --- I have looked a little further and found that: 1. There is no generator script /usr/lib/udev/rules.d/75-persistent-net-generator.rules any more in 13.1. Was that one left out on purpose or is it standard with udev 208? Maybe one has to always define the NIC names via "yast network" now? Otherwise, I am at a loss as to where the /etc/udev/rules.d/70-persistent-net.rules comes from. Under 12.3, there seems to be some special handling for VM and Realtek NICs in the generator script: # ignore KVM virtual interfaces ENV{MATCHADDR}=="52:54:00:*", GOTO="persistent_net_generator_end" # ignore VMWare virtual interfaces ENV{MATCHADDR}=="00:0c:29:*|00:50:56:*", GOTO="persistent_net_generator_end" # ignore Hyper-V virtual interfaces ENV{MATCHADDR}=="00:15:5d:*", GOTO="persistent_net_generator_end" My VM MACs started with "52:54:00:", so the different naming happens probably only for VM machines. 2. I have now migrated a non-VM machine with an Intel E1000 NIC and everything worked fine with that one. The rules in question are given in comment #1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=850732 https://bugzilla.novell.com/show_bug.cgi?id=850732#c10 --- Comment #10 from Uwe Meyer-Gruhl 2013-11-18 13:34:10 UTC --- I doubt that VM MACs change at each boot - they are ramdomly created when the VM guest is created. Most probably the NIC name was assigned in the 70-persistent-net.rules when the first configuration by the installation process for 12.3 was done and not by the generator rule. Under 13.1, one can choose in YaST on how (i.e. based on PCI slot or on MAC) the persistent name should be assigned and a 70-persistent-net.rules file is created (which effectively defeats systemd/udev standard rules). So, after all, the new scheme MAY give problems depending on how the old persistent rules have been created. The new NIC naming scheme should at least be listed in the 13.1 release notes and in the online distribution upgrade instructions. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=850732 https://bugzilla.novell.com/show_bug.cgi?id=850732#c12 --- Comment #12 from Marius Tomaschewski 2013-11-20 22:23:31 UTC --- (In reply to comment #6)

Well, then that has nothing to do with udev. If the rules where generated correctly it would work as expected.

The best way is to use the mac address, that doesn't change at all (at least it shouldn't).

This is not completely correct. MAC based matching is unusable for bonding [it usually a bond sets the MAC of the primary slave on _all_ slaves and stays with this MAC]. You need BUS based rule as you want to be able to replace the NIC with a different one [e.g. PCI hotplug] and the new NIC has to get the same name as the NIC before to be enslaved automatically. (In reply to comment #7)

BTW, how do you even generate a rule in yast? I've tried 13.1, but didn't see anything something like that.

It were working up to IMO 12.3 -- when not, is IMO a bug as it breaks bonding. (In reply to comment #11)

The naming scheme is not the issue, your problem is the way the rule has been create and by what. In previous version of udev there was a script called by 75-persistent-net-generator.rules called write_net_rules which never based itself on BUS_ID or something similar, always on mac address.

Ahm... it were generating MAC based rules for ethernet by default, but in some cases the rules were AFAIR always BUS based -- e.g. s390, ... And when there were bonding configured on top of an interface, the rule has to be rewritten to BUS based one. Otherwise hotplugging does not work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=850732 https://bugzilla.novell.com/show_bug.cgi?id=850732#c Robert Milasan changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |mfilka@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.