[Bug 848803] New: Ethernet card has duplicate configurations, "ifup" does not work (on new install)
https://bugzilla.novell.com/show_bug.cgi?id=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c0 Summary: Ethernet card has duplicate configurations, "ifup" does not work (on new install) Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nrickert@ameritech.net 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 This is from an install of 13.1RC2 today. I installed with manual configuration. The network config page showed a WiFi card, and two ethernet cards which looked identical. As far as I know, this computer has only one ethernet card. I accepted the defaults. The network failed to start (network tests during configuration). Backing up, I switched to NetworkManager, and then the network test succeeded. Other relevant information: During install, I configured the installer to also use online repos. Perhaps that is related (since it uses the network) The ethernet card entries appear to have device names: "enp4s0" and "p5p1". The error message after network tests was a failure on "enp4s0". NetworkManager is successfully use "p5p1". Opensuse 12.3 on this box is using "p5p1". My guess is that if I go into network settings and delete "enp4s0", that will correct the problem. But I have not tried this. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c1 --- Comment #1 from Neil Rickert <nrickert@ameritech.net> 2013-11-03 20:17:06 UTC --- Created an attachment (id=565982) --> (http://bugzilla.novell.com/attachment.cgi?id=565982) compressed tar of /var/log/YaST2 Attaching the Yast logs for the install. It looks to me as if the install correctly used device "p5p1" for the online repos. I'm not sure where device "enp4s0" comes from. The MAC address showing in the logs for "enp4s0" is identical to the MAC address for "p5p1". -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c zhang jiajun <jzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jzhang@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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c2 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rmilasan@suse.com Component|Network |Network Version|Final |RC 2 AssignedTo|mt@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com Product|openSUSE 12.3 |openSUSE 13.1 Target Milestone|--- |Final --- Comment #2 from Marius Tomaschewski <mt@suse.com> 2013-11-04 11:29:08 UTC --- Fixed Product to 13.1 as in comment 0. The p5p1 is a name which is generated by biosdevname. enp4s0 is the name used by new systemd/udevd name. So there seems to be either some inconsistence it yast2 bug. When I've seen this correctly, on some installation images, biosdevname is still used by default [initrd]. Maybe it is fixed in the meantime. ifup behaves correctly: when there is an interface config, it is trying to start it and wait for it [except in e.g. STARTMODE=hotplug]. The ifcfg config has to match the interface name. -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mt@suse.com AssignedTo|bnc-team-screening@forge.pr |mfilka@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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c3 --- Comment #3 from Marius Tomaschewski <mt@suse.com> 2013-11-04 11:39:19 UTC --- (In reply to comment #0)
My guess is that if I go into network settings and delete "enp4s0", that will correct the problem. But I have not tried this.
I'd say another way around: AFAIS in y2log, the config name is "ifcfg-p5p1" while the name is enp4s0: "p":$["p5p1":$["BOOTPROTO":"dhcp4", "NAME":"RTL8111/8168B PCI Express Gigabit Ethernet controller", "STARTMODE":"auto"] 1:$["hwinfo":$["active":true, "bus":"pci", "busid":"0000:04:00.0", "dev_name":"enp4s0", "driver":"r8169", " A mv /etc/sysconfig/network/ifcfg-p5p1 /etc/sysconfig/network/ifcfg-enp4s0 [and migration of other variables which may use it] should fix 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c4 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |nrickert@ameritech.net --- Comment #4 from Michal Filka <mfilka@suse.com> 2013-11-04 12:02:18 UTC --- Is it upgrade of an older installation? It seems as a problem of conversion from older naming scheme (biosdevname in this case) to new one (systemd) -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c5 Neil Rickert <nrickert@ameritech.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|nrickert@ameritech.net | --- Comment #5 from Neil Rickert <nrickert@ameritech.net> 2013-11-04 15:05:07 UTC --- This was a new installation, on top of an older installation. I preserved "/home", but the root partition was reformatted for the install. It's possible that the installer imports older configuration details. I don't know how to tell that. It does import ssh-host-keys from the previous system. -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c6 Dave Davey <daved@windclimber.id.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |daved@windclimber.id.au --- Comment #6 from Dave Davey <daved@windclimber.id.au> 2013-11-06 11:36:01 UTC --- I am having a similar problem with RC2. "Traditional" network setup does not work with either ethernet (new name enp0s25) or wireless (new name wlp3s0). I see messages like "Dependency failed for ifup managed network interface wlp3s0". I have seen references to iplugd in some messages. iplugd never seems to be running. If I try to start it manually, I get errors about not finding eth0, regardless of editing iplugd.config. I also note that the LINKLOCAL_INTERFACES line in /etc/sysconfig/network/config has no provision for the new interface 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c Dave Davey <daved@windclimber.id.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c7 --- Comment #7 from Marius Tomaschewski <mt@suse.com> 2013-11-15 14:50:02 UTC --- (In reply to comment #6)
I am having a similar problem with RC2. "Traditional" network setup does not work with either ethernet (new name enp0s25) or wireless (new name wlp3s0). I see messages like "Dependency failed for ifup managed network interface wlp3s0".
Hmm... dependency failed? Sounds like something new and different to this bug. I'd say please open a new bug report and assign to me.
I also note that the LINKLOCAL_INTERFACES line in /etc/sysconfig/network/config has no provision for the new interface names.
Hmm. true. But this just causes to not to set any 169.254.0.0/16 (zeroconf); we have a fate request to disable this miss-feature by default anyway... -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c8 --- Comment #8 from Marius Tomaschewski <mt@suse.com> 2013-11-15 15:18:34 UTC --- (In reply to comment #7)
(In reply to comment #6)
I am having a similar problem with RC2. "Traditional" network setup does not work with either ethernet (new name enp0s25) or wireless (new name wlp3s0). I see messages like "Dependency failed for ifup managed network interface wlp3s0".
Hmm... dependency failed? Sounds like something new and different to this bug. I'd say please open a new bug report and assign to me.
Just an idea... what you can to try out is to check if this helps: Edit /usr/lib/systemd/system/network.service and set Type=oneshot in the [Service] section instead of Type=forking. -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c9 --- Comment #9 from Neil Rickert <nrickert@ameritech.net> 2013-11-20 15:33:47 UTC --- I didn't try your suggestion. I've just finished installing 13.1 final on the same box. And that went smoothly. This problem did not show up. The network is configured properly with "/etc/sysconfig/network/ifcfg-enp4s0". However, there was a difference in how I installed. This time, I did not add online repos for the install, partly because I suspect adding those might be related. Sometime in the next week, I'll try an experimental install, adding online repos, to see what happens. -- 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=848803 https://bugzilla.novell.com/show_bug.cgi?id=848803#c10 --- Comment #10 from Neil Rickert <nrickert@ameritech.net> 2013-11-30 23:24:06 UTC --- A final (I hope) update to this bug. I did another install on the same box (but to an external drive). For this install, I did choose to add online repos for the install. Early in the install, there was a section for configuring network devices to access the online repos. It named the ethernet device "p5p1". After completing the install (I used "automatic configuration"), there was no network. Going into Yast network settings, I deleted the configuration for "p5p1". I then switch to "NetworkManager". And, after completing, I now had a network connection. NetworkManager was using "enp4s0" for the network. So it looks pretty clear -- the bad network configuration is coming from the installer when configuring online repos for the install. The configuration used by the installer is copied to the installed system, causing the problem. Presumably, the DVD is using the old naming scheme, but the software it installs uses the new naming scheme. It's obviously too late to fix this for 13.1, but I hope it can be avoided for 13.2. -- 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