[Bug 845649] New: 70-persistent-net.rules is empty
https://bugzilla.novell.com/show_bug.cgi?id=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c0 Summary: 70-persistent-net.rules is empty Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: thomas.e.schreiner@t-online.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 the file /etc/udev/rules.d/70-persistent-net.rules is emtty. tes04:/etc/udev/rules.d # ll 70-persistent-net.rules -rw-r--r-- 1 root root 0 Oct 13 15:52 70-persistent-net.rules Reproducible: Always Steps to Reproduce: 1. New Installation of openSUSE 13.1 RC1 and reboot 2. ifconfig : netwok interface enp3s0f2 Link encap:Ethernet HWaddr 00:90:F5:E0:7B:D5 for netcard "03:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 0a)" 3. Actual Results: We had the same Problem at the beginning with openSUSE 12.3. The problem has been fixed after a while by patch. Expected Results: without a working udev rules you are unable to control the numbering of your interfaces. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c1 Thomas E. Schreiner <thomas.e.schreiner@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.e.schreiner@t-online | |.de --- Comment #1 from Thomas E. Schreiner <thomas.e.schreiner@t-online.de> 2013-10-13 17:09:32 UTC --- After copying a file /etc/udev/rules.d/70-persistent-net.rules from older openSUSE 12.3 partition into /etc/udev/rules.d/ of 13.1 partition and doing a reboot, I got normal Interface names, as you can see here : tes04:~ # ifconfig br0 Link encap:Ethernet HWaddr 00:90:F5:E0:7B:D5 inet addr:192.168.13.4 Bcast:192.168.13.63 Mask:255.255.255.192 inet6 addr: fe80::290:f5ff:fee0:7bd5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:790 errors:0 dropped:0 overruns:0 frame:0 TX packets:807 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:396276 (386.9 Kb) TX bytes:119170 (116.3 Kb) eth0 Link encap:Ethernet HWaddr 00:90:F5:E0:7B:D5 inet6 addr: fe80::290:f5ff:fee0:7bd5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:819 errors:0 dropped:0 overruns:0 frame:0 TX packets:815 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:409456 (399.8 Kb) TX bytes:119818 (117.0 Kb) -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem AssignedTo|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |werner@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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c2 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |fcrozat@suse.com, | |mt@suse.com, | |rmilasan@suse.com InfoProvider| |rmilasan@suse.com --- Comment #2 from Dr. Werner Fink <werner@suse.com> 2013-10-24 07:49:47 UTC --- It becomes rather boring now: Why the patch 1026-re-add-persistent-net.patch had been removed? It does not look like that is a unused patch. It was my bug report bnc#809843 for which Robert had add this patch to resolve this issue. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c3 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|rmilasan@suse.com | --- Comment #3 from Robert Milasan <rmilasan@suse.com> 2013-10-24 08:07:16 UTC --- Werner, this is normal. systemd/udev has Predictable Names enabled and Persistent naming has been dropped. If you want use persistent naming, you disable predictable names and create manually your own rule (which is up to you). http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c4 --- Comment #4 from Robert Milasan <rmilasan@suse.com> 2013-10-24 08:08:16 UTC --- Also in 12.3 was a different issue, no setup/rule to name the network devices which where left up to the kernel to name, which causes issues. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c5 --- Comment #5 from Thomas E. Schreiner <thomas.e.schreiner@t-online.de> 2013-10-24 16:03:02 UTC --- One further issue I found out was, that XEN will have problems with network device names like "enp3s0f2", what you get without 70-persistent-net.rules, as I noted in Bug #845648. Here an example from the /var/log/messages : 2013-10-13T17:00:52.972103+00:00 tes04 libvirtd[4726]: udev reports device 'enp3s0f2' does not have property 'DRIVER' 2013-10-13T17:00:52.972584+00:00 tes04 libvirtd[4726]: Found property key 'SUBSYSTEM' value 'net' for device with sysname 'enp3s0f2' 2013-10-13T17:00:52.972947+00:00 tes04 libvirtd[4726]: Found property key 'INTERFACE' value 'enp3s0f2' for device with sysname 'enp3s0f2' 2013-10-13T17:00:52.973305+00:00 tes04 libvirtd[4726]: Found sysfs attribute 'address' value '00:90:f5:e0:7b:d5' for device with sysname 'enp3s0f2' 2013-10-13T17:00:52.973697+00:00 tes04 libvirtd[4726]: Found sysfs attribute 'addr_len' value '6' for device with sysname 'enp3s0f2' 2013-10-13T17:00:52.974051+00:00 tes04 libvirtd[4726]: Converted '6' to unsigned int 6 and some lines later ... : 2013-10-13T17:16:58.834950+00:00 tes04 libvirtd[2182]: skipping syntax unsupported interface enp3s0f2 2013-10-13T17:21:56.940025+00:00 tes04 libvirtd[2182]: message repeated 1498 times: [ skipping syntax unsupported interface enp3s0f2] 2 The rest You can read in my comment from 2013-10-13 17:09:32 UTC above. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c6 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |rmilasan@suse.com --- Comment #6 from Dr. Werner Fink <werner@suse.com> 2013-10-25 06:54:04 UTC --- (In reply to comment #4) (In reply to comment #3) This breaks existing and already perfect working netsetups ... is this a typical systemd/udev upstream ruthless behaviour? IMHO it should be possible to disable the socalled Predictable Names to prefere the Human Readable Names in case of a) an update and b) in case this is required by e.g. XEN. (In reply to comment #5) IMHO you should ask upstream about this ruthless behaviour as it breaks the common usage of Human Readable Names. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c7 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|rmilasan@suse.com | --- Comment #7 from Robert Milasan <rmilasan@suse.com> 2013-10-25 07:04:39 UTC --- Upstream knows about this and the persistent net rules have been dropped since version 195 or so. We could do some workaround, but if you already have a persistent rule in the system, it should work like before, you maybe will need to disable the predictable rule with net.ifnames=0. The other part is that I wouldn't like to support something that is unsupported, like persistent names/rules. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c8 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |rmilasan@suse.com --- Comment #8 from Dr. Werner Fink <werner@suse.com> 2013-10-25 07:55:42 UTC --- (In reply to comment #7) Hmmm ... IMHO we can not drop support for things like XEN, can we? Beside this: is there any way to map the `Predictable (but unreadable) Names' onto the `Persistent and Human Readable Names' ... Compare with https://fedoraproject.org/wiki/Talk:Features/ConsistentNetworkDeviceNaming http://fedoraforum.org/forum/showthread.php?t=274730 -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c9 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|rmilasan@suse.com | --- Comment #9 from Robert Milasan <rmilasan@suse.com> 2013-10-25 08:22:48 UTC --- If Xen has an issue with this new names that means is Xen the problem. Naming a network device weirdly doesn't mean is broken, means Xen is. There should be some support in YaST for naming the network more 'acceptable' for the user, just not sure exactly how. Haven't tried it. Adding the persistent rules can be done easily, but there is always the issue who comes first. Meaning do we use by default Predictable Names or Persistent Names. I'm going with Predictable Names even if they look weird, at least they are supported upstream and work well. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c10 --- Comment #10 from Thomas E. Schreiner <thomas.e.schreiner@t-online.de> 2013-10-25 08:48:17 UTC --- (In reply to comment #7)
Upstream knows about this and the persistent net rules have been dropped since version 195 or so. We could do some workaround, but if you already have a persistent rule in the system, it should work like before, you maybe will need to disable the predictable rule with net.ifnames=0.
The other part is that I wouldn't like to support something that is unsupported, like persistent names/rules.
I had a 70-persistent-net.rules for this system just because I installed 13.1 parallel to 12.3 on the second Disk. Mostly I have to make a new Installation on new hardware. So maybe, I'm able to build my own 70-persistent-net.rules, but how long will this work, while persistent-net.rules are officially deprecatetd? -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c11 --- Comment #11 from Robert Milasan <rmilasan@suse.com> 2013-10-25 09:00:35 UTC --- The generation of persistent rules is out, but the support is there. I've added the support for this so users can manually generate/create their own persistent rule and of course use them. There 2 things need it to be done: 1. disable the predictable names using net.ifnames=0 at boot time. 2. generate your own persistent rule in /etc/udev/rules.d. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c12 --- Comment #12 from Thomas E. Schreiner <thomas.e.schreiner@t-online.de> 2013-10-25 16:10:33 UTC --- (In reply to comment #11)
The generation of persistent rules is out, but the support is there. I've added the support for this so users can manually generate/create their own persistent rule and of course use them.
There 2 things need it to be done:
1. disable the predictable names using net.ifnames=0 at boot time. 2. generate your own persistent rule in /etc/udev/rules.d.
I don't want to brake up a academical dispute about the sense of using predictable names or alias names. From Solaris 11 I known how useful alias names like eth0 or net0 are. Especially if you are writing firewall rules with iptables -A INPUT -j DROP -i eth0 ... for several machines and each machine has another interface name, you get in trouble. Cluster-Rules with with interface dependent rules might get problems if you are unable to bring even names in the right enumeration. I'm able to give you more examples if you want, apart from this, that these name are wired. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c13 --- Comment #13 from Dr. Werner Fink <werner@suse.com> 2013-10-28 07:54:20 UTC --- (In reply to comment #12) I fully agree ... the idea and implemenataion of `predictable' names was done by udev/systemd upstream and in experience it become difficult to change this. In fact the udev part of systemd includes a patch from Robert to make it possible to rename existing network device. This is the reas on why I have suggested to report this upstream (comment #6 last few lines). With your exemplification it may happen that Kay is willingly to broaden his mind ;) -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c14 --- Comment #14 from Thomas E. Schreiner <thomas.e.schreiner@t-online.de> 2013-10-31 18:39:49 UTC --- I've done a upgrade from 13.1 RC1 to 13.1 RC2 and done at test to install a 13.1RC2 VM with the virtual machine manager. The first Result was, that pushing the Browse button in the Menu Virtual Disk causes a hang of the VMM, which I had to kill with Ctrl+Alt+ESC. On the second round I copied path and file name and enden the configuration like you can see in picture Error_RC2-4.png.A view seconds after pressing the OK button and after 3/4 of the green progress bar I got the well known error message. attachements : /var/log/messages file of today 3 screen shots -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c15 --- Comment #15 from Thomas E. Schreiner <thomas.e.schreiner@t-online.de> 2013-10-31 18:43:04 UTC --- Sorry, wrong bug number. -- 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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com AssignedTo|werner@suse.com |systemd-maintainers@suse.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=845649 https://bugzilla.novell.com/show_bug.cgi?id=845649#c Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- OS/Version|SUSE Other |openSUSE 13.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.
participants (1)
-
bugzilla_noreply＠novell.com