[Bug 810478] New: no network in second stage install because udev renames network interface to em1
https://bugzilla.novell.com/show_bug.cgi?id=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c0 Summary: no network in second stage install because udev renames network interface to em1 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers@suse.de ReportedBy: ohering@suse.com QAContact: jsrain@suse.com Found By: Outsourced Testing Blocker: --- If the installation of 12.3 is started with these cmdline options, the second stage fails to start any network because initially there is an 'ifcfg-eth0' file, but for some reasons udev renames eth0 to em1. There is appearently not a single config file which tells udev to do that, I havent found the string 'em1' in /usr /etc /var quiet panic=9 sysrq=yes start_shell dhcp=1 install=http://192.168.2.100/dist/loop/12.3/x86_64/dvd1/ ssh=1 sshpassword=root nosshkey vnc=1 vncpassword=password -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c1 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |rmilasan@suse.com --- Comment #1 from Thomas Fehr <fehr@suse.com> 2013-03-20 10:10:26 UTC --- Reassigned to udev maintainer -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c2 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ohering@suse.com --- Comment #2 from Robert Milasan <rmilasan@suse.com> 2013-03-20 10:18:20 UTC --- Not sure how is this possible, udev in 12.3 doesn't handle the network at all, meaning there are no rules to rename the network 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c3 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ohering@suse.com | --- Comment #3 from Olaf Hering <ohering@suse.com> 2013-03-20 11:38:40 CET --- Just google for eth0 em1, its biosdevname and yast is appearently not aware of that renaming. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c4 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ohering@suse.com --- Comment #4 from Robert Milasan <rmilasan@suse.com> 2013-03-20 10:43:56 UTC --- then boot with biosdevname=0, but still is not udev, seems you have biosdevname in the installer which is not usual. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c5 --- Comment #5 from Olaf Hering <ohering@suse.com> 2013-03-20 11:52:52 CET --- It is wrong to require any additional kernel cmdline option just because two tools are not aware of each other. Later I will do another network install to a second partition and see what happens in first and second stage with udev rules, or the lack of such rules. And dmesg has 'systemd-udev[X] rename interface eth0 to em1', or similar. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c6 --- Comment #6 from Robert Milasan <rmilasan@suse.com> 2013-03-20 10:57:44 UTC --- It's not wrong, I don't work with yast or anything like this. biosdevname as an intent if it's installed, to setup the network has the BIOS provides them, nothing to do with udev, thats the hole point of biosdevname. I didn't come up with this, its just how it is. It's really nothing that I can do, as long as you use biosdevname you or the installer needs to expect that the network will be or can be different. If the installer doesn't support it, then the installer should be fixed. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c7 --- Comment #7 from Robert Milasan <rmilasan@suse.com> 2013-03-20 11:00:13 UTC --- (In reply to comment #6)
It's not wrong, I don't work with yast or anything like this. biosdevname as an intent if it's installed, to setup the network has the BIOS provides them,
This doesn't make sense, what I wanted to say is that if you have hardware that does support biosdevname and you have biosdevname setup it is expected that the network devices will be named according to the BIOS names and not eth0 or anything like that. And again, nothing wrong with udev, yast2 or some other related apps need to support this. In SLES is supported, don't know why is not in openSUSE. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c8 Robert Milasan <rmilasan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low AssignedTo|rmilasan@suse.com |duwe@suse.com --- Comment #8 from Robert Milasan <rmilasan@suse.com> 2013-03-20 12:42:29 UTC --- This is biosdevname related so assigning it to Torsten. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c9 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ohering@suse.com | AssignedTo|duwe@suse.com |yast2-maintainers@suse.de --- Comment #9 from Olaf Hering <ohering@suse.com> 2013-03-20 14:38:47 CET --- In first stage, if booted with start_shell, the interface is named eth0. So yast must assume that this is the persistant name. inst-sys does not include biosdevname. I think it should be added (not without adding explicit support for it to various tools!) to get consistant naming. In the running system yast still can not deal with the renamed interface, it always talks about eth0, while in fact the interface is named em1 in my case. Its name could be very well "foo" or "bar". To make that long story short, yast2 network was not adjusted properly when biosdevname was placed into the default selection. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c10 --- Comment #10 from Robert Milasan <rmilasan@suse.com> 2013-03-20 13:42:34 UTC --- Olaf the maintainer of yast2-network is Michal Filka, maybe you should assign it to him. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c11 --- Comment #11 from Olaf Hering <ohering@suse.com> 2013-03-20 15:07:45 CET --- Created an attachment (id=530670) --> (http://bugzilla.novell.com/attachment.cgi?id=530670) bug810478.tar.bz2 Attaching logfiles from first-stage. If the persistant rules still work (no idea if they still do) yast was not adapted to udev changes. 192:~/bug810478 # grep persist /var/log/YaST2/y2log 2013-03-20 15:00:43 <3> 192.168.2.129(3102) [YCP] clients/copy_files_finish.ycp:125 Cannot copy non-existent file: /etc/udev/rules.d/70-persistent-cd.rules 2013-03-20 15:00:43 <3> 192.168.2.129(3102) [YCP] clients/copy_files_finish.ycp:125 Cannot copy non-existent file: /etc/udev/rules.d/70-persistent-net.rules 2013-03-20 15:02:14 <1> 192.168.2.129(3102) [YCP] clients/save_network.ycp:586 net_destfile /mnt/etc/udev/rules.d/70-persistent-net.rules 2013-03-20 15:02:14 <1> 192.168.2.129(3102) [YCP] clients/save_network.ycp:600 Copying 70-persistent-net.rules to the installed system 2013-03-20 15:02:14 <3> 192.168.2.129(3102) [bash] ShellCommand.cc(shellcommand):78 /bin/cp: cannot stat ‘/etc/udev/rules.d/70-persistent-net.rules’: No such file or directory -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c12 --- Comment #12 from Robert Milasan <rmilasan@suse.com> 2013-03-20 14:25:14 UTC --- Well this is the problem, I had to re-add the persistent rules back as it was creating a mess with the network devices, but thats not available in the installer and was submitted only now. Upstream of systemd/udev have dropped persistent rules for network, cdrom, etc, but at the time there wasn't any 'alternative' and seems the only thing I could have done now is to add the persistent rules back. Still the persistent rules have nothing to do with your network being named em1, even if the persistent rules would be there and working, biosdevname would named eth0 to em1. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c13 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mfilka@suse.com --- Comment #13 from Thomas Fehr <fehr@suse.com> 2013-03-20 14:30:40 UTC --- Reassigning to maintainer of yast2-network -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c14 --- Comment #14 from Olaf Hering <ohering@suse.com> 2013-03-20 16:03:41 CET --- Created an attachment (id=530679) --> (http://bugzilla.novell.com/attachment.cgi?id=530679) bug810478-second-stage.tar.bz2 various logs from installed system. yast does not recognize em1, it only knows about eth0 -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c15 --- Comment #15 from Olaf Hering <ohering@suse.com> 2013-03-21 15:37:42 CET --- I think the issue is just that biosdevname is not in inst-sys because the system has just one NIC. YaST shows two because it appearently thinks ifcfg-eth0 is a valid config for a non-existant card. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c16 --- Comment #16 from Michal Filka <mfilka@suse.com> 2013-07-19 07:54:57 UTC --- I've prepared a set of patches for yast to make it aware of device renaming. Hopefully, they make will it into M4. it is fixed in: - yast2-network.rpm 2.25.7 - yast2.rpm 2.24.5 I would like to ask you for retesting then. I don't have biosdevname hw available. See also bnc#695262. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ohering@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.
https://bugzilla.novell.com/show_bug.cgi?id=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c17 --- Comment #17 from Michal Filka <mfilka@suse.com> 2013-07-19 07:55:58 UTC --- I've talked about OpenSUSE 13.1 M4 in Comment#16. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c18 --- Comment #18 from Olaf Hering <ohering@suse.com> 2013-07-31 20:01:31 CEST --- biosdevname is still not in inst-sys in 13.1 M3. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c19 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@suse.com --- Comment #19 from Michal Filka <mfilka@suse.com> 2013-08-27 04:59:54 UTC --- *** Bug 769417 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=769417 -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c20 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|ohering@suse.com |snwint@suse.com --- Comment #20 from Michal Filka <mfilka@suse.com> 2013-08-27 08:12:24 UTC --- Steffen, what is status of biosdevname in instsys? -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c21 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|snwint@suse.com | --- Comment #21 from Steffen Winterfeldt <snwint@suse.com> 2013-08-27 11:03:18 CEST --- added to Factory now -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c22 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ohering@suse.com --- Comment #22 from Michal Filka <mfilka@suse.com> 2013-08-27 09:10:17 UTC --- Olaf, could you retest it? -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c23 --- Comment #23 from Olaf Hering <ohering@suse.com> 2013-09-03 17:18:22 CEST --- (In reply to comment #22)
Olaf,
could you retest it?
Will do it with the next 13.1 milestone. -- 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=810478 https://bugzilla.novell.com/show_bug.cgi?id=810478#c24 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ohering@suse.com | --- Comment #24 from Olaf Hering <ohering@suse.com> 2013-09-26 16:34:16 CEST --- So wether this is fixed depends on the way you view it: in 13.1b1 inst-sys, due to usage of biosdevname, the interface is now em1 After disabling /etc/udev/rules.d/70-persistent-net.rules: in installed system, if biosdevname is present, the interface is em1 in installed system, if biosdevname is not present, the interface is eno1 -- 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.
http://bugzilla.novell.com/show_bug.cgi?id=810478 Olaf Hering <ohering@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #25 from Olaf Hering <ohering@suse.com> --- this is fixed in sle12. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com