[Bug 903972] New: System upgrade procedure from DVD from 13.1 to 13.2 fails because it cannot setup the network
http://bugzilla.opensuse.org/show_bug.cgi?id=903972 Bug ID: 903972 Summary: System upgrade procedure from DVD from 13.1 to 13.2 fails because it cannot setup the network Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening@forge.provo.novell.com Reporter: stakanov@freenet.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- Try to setup the new 13.2 on a Lenovo 201 with or without docking station. Although the network is present and the machine branched directly to the modem router the networksetupprocedure will stay on the dialog choice between "setup the network now" yes or no, because it just jumps back to it. Either no network is found or the dialogue is hanging? As a result, no internetconnection is found and all repos are lost. A real upgrade is therefore not possible from DVD-64. You get of course a big bunch of missing dependencies. This is constant, whether you use the ultrabase for the installation or the standalone notebook. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Maciej Pilichowski
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #3 from Stakanov Schufter
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Maciej Pilichowski
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #5 from Maciej Pilichowski
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #6 from Stakanov Schufter
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #7 from James Rome
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #8 from James Rome
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #9 from James Rome
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #10 from Maciej Pilichowski
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Bernhard Wiedemann
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Michal Filka
Same problem with dvd upgrade. My nic is RTL8111/8168B. My v13.1 kernel shows the driver to be r8169. The processor is Intel(R) Core(TM) i7-3770 CPU
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) Subsystem: Dell Device 0546 Flags: bus master, fast devsel, latency 0, IRQ 45 I/O ports at d000 [size=256] Memory at f0004000 (64-bit, prefetchable) [size=4K] Memory at f0000000 (64-bit, prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=4 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Kernel driver in use: r8169 Kernel modules: r8169
Checking v13.2 VT console lspci -v shows kernel driver r8169. wicked ifstatus eth0 displays "interface not found"
lets start from this comment. YaST asks for manual configuration only if it is not able to do it automatically. If wicked cannot see it, it is nothing YaST can help with. @wicked team: could you pls look into it? thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Pawel Wieczorkiewicz
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #14 from James Rome
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #15 from Pawel Wieczorkiewicz
Part of the problem may be that eth0 is no longer the name for the interface! ifconfig enp0s25 Link encap:Ethernet HWaddr 00:22:68:66:D6:1B inet addr:192.168.1.70 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::222:68ff:fe66:d61b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:659391549 errors:0 dropped:19602 overruns:0 frame:0 TX packets:1053673459 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:725190151359 (691595.2 Mb) TX bytes:1253496015141 (1195426.9 Mb) Interrupt:20 Memory:f7dc0000-f7de0000
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:714549 errors:0 dropped:0 overruns:0 frame:0 TX packets:714549 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5107630902 (4871.0 Mb) TX bytes:5107630902 (4871.0 Mb)
This is exaclt what I was suspecting... thus the command:
wicked ifstatus eth0 displays "interface not found" would not work.
Since systemd renames the interfaces according to it's view, ifcfg-* config files names must be updated along. BTW: the fancy systemd style names can be disabled by kernel cmdline param net.ifnames=0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #16 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #17 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #18 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #19 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #20 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Pawel Wieczorkiewicz
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Pawel Wieczorkiewicz
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #22 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #23 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #24 from James Rome
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
Josef Reidinger
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #25 from Pawel Wieczorkiewicz
Why did 13.2 change the name of the ethernet port? People are expecting to use the old, simple names.
Take a look here: http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #26 from Michal Filka
Part of the problem may be that eth0 is no longer the name for the interface! ifconfig enp0s25 Link encap:Ethernet HWaddr 00:22:68:66:D6:1B inet addr:192.168.1.70 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::222:68ff:fe66:d61b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:659391549 errors:0 dropped:19602 overruns:0 frame:0 TX packets:1053673459 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:725190151359 (691595.2 Mb) TX bytes:1253496015141 (1195426.9 Mb) Interrupt:20 Memory:f7dc0000-f7de0000
it seems to me that automatic configuration succeeded here, network is configured and you should be able to proceed. And you shouldn't see "setup network dialog" in this case. Ccing installer maintainer to get his attention ;-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #27 from James Rome
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #28 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #29 from Jon Harrison
in case of upgrade: - yast do not touch network configuration. Configuration is left as is in target. - yast tries to setup network at the beginning of installation only. Just for other installer parts needs. However it cannot use setup from older installation bcs it is not know to installer at this phase. This configuration is temporary and when the system is rebooted into installed system, the configuration present here is used. So, you can probably need to disable systemd's predictable interface device names if you haven't used them so far. (See comment#15) - installer shows manual network configuration only if is not able to configure the network automatically
If anything from the above doesn't work for you, then it would be best to provide us yast logs from install time.
I am including the entire /var/log directory plus additional files . Please note that in my situation, I am trying to upgrade v13.1 booting from DVD. A prior comment about Network Manager running does not mean anything to me since how can it be running if YaST2 is starting an install? If it is running I have no knowledge of that. I want to be clear that I have not completed an install of v13.2 because I don't believe I should need to go to a VT to create a network connection. The upgrade should do this for me. So every time I experiment with this I abort the install before anything is written to my system. The attached file "update-logs.zip" is from the following point in the update: Mount Partition, Remove Prior repositories, Read list of Online Repositories, fails and requests that I configure Network. Click 'Yes' and nothing happens. The logs in the zip are taken at this point. Now, I open a VT and create a connection by dhcpcd p3p2. At this point, I can switch back to YaST2 and continue the update, which I abort after the next screen as I don't wish to continue, I'd rather wait for the installer to be fixed. I am also attaching "add-network.zip" which contain the only logs that changed during creating the connection in the VT. That zip contains the file 'messages' and 'wickedd.log' and show the changes due to bringing up the network connection. I hope this helps someone figure out why doing an update fails for me. Rgds, Jon -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
--- Comment #30 from Jon Harrison
http://bugzilla.opensuse.org/show_bug.cgi?id=903972
http://bugzilla.opensuse.org/show_bug.cgi?id=903972#c31
Stakanov Schufter
participants (1)
-
bugzilla_noreply@novell.com