[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 <bluedzins@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bluedzins@wp.pl --- Comment #1 from Maciej Pilichowski <bluedzins@wp.pl> --- Btw. when you run installation the first step after EULA is configuration of network card. But when you run upgrade, after EULA there is no such step, the upgrader goes right to selecting the system partition. The above described dead-loop is bad, but keeping inconsistent steps between installer and upgrader is bad as well. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |lslezak@suse.com --- Comment #2 from Bernhard Wiedemann <bwiedemann@suse.com> --- Would be nice, if you could attach output of lspci -nn just in case it depends on the type of Ethernet device. -- 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 #3 from Stakanov Schufter <stakanov@freenet.de> --- Desired output of lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02) 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) 00:19.0 Ethernet controller [0200]: Intel Corporation 82577LM Gigabit Network Connection [8086:10ea] (rev 06) 00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 06) 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06) 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 06) 00:1c.3 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 [8086:3b48] (rev 06) 00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 06) 00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 06) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a6) 00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller [8086:3b07] (rev 06) 00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b2f] (rev 06) 00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 06) 00:1f.6 Signal processing controller [1180]: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem [8086:3b32] (rev 06) 02:00.0 Network controller [0280]: Intel Corporation Centrino Ultimate-N 6300 [8086:4238] (rev 35) ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 02) ff:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 02) ff:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 02) ff:02.1 Host bridge [0600]: Intel Corporation 1st Generation Core Processor QPI Physical 0 [8086:2d11] (rev 02) ff:02.2 Host bridge [0600]: Intel Corporation 1st Generation Core Processor Reserved [8086:2d12] (rev 02) ff:02.3 Host bridge [0600]: Intel Corporation 1st Generation Core Processor Reserved [8086:2d13] (rev 02) This with the docking station in place. The update went smooth with zypper dup from the CLI having the old 13.1 in place. Second annoying thing: when the upgrade fails, all repos are eliminated from the old installation. So you have to set them up again by hand. -- 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 <bluedzins@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jamesrome@alum.mit.edu --- Comment #4 from Maciej Pilichowski <bluedzins@wp.pl> --- *** Bug 904124 has been marked as a duplicate of this bug. *** -- 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 #5 from Maciej Pilichowski <bluedzins@wp.pl> --- Another computer, this time with cable connection, no network configuration step as well. So in total for now, we know about 4 cases this step is missing. I doubt it has anything to do with network card, there is no such step (compare to it to regular installation; vs. upgrade). -- 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 #6 from Stakanov Schufter <stakanov@freenet.de> --- Maciej, a question. Are all these laptops from Lenovo? Or are there other brands involved? -- 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 #7 from James Rome <jamesrome@alum.mit.edu> --- Here is my lspci output (lenovo X1 (2014): 00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b) 00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) 00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 0b) 00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC [8086:9c31] (rev 04) 00:16.0 Communication controller [0780]: Intel Corporation 8 Series HECI #0 [8086:9c3a] (rev 04) 00:16.3 Serial controller [0700]: Intel Corporation 8 Series HECI KT [8086:9c3d] (rev 04) 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I218-LM [8086:155a] (rev 04) 00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio Controller [8086:9c20] (rev 04) 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 6 [8086:9c1a] (rev e4) 00:1c.1 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 3 [8086:9c14] (rev e4) 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series USB EHCI #1 [8086:9c26] (rev 04) 00:1f.0 ISA bridge [0601]: Intel Corporation 8 Series LPC Controller [8086:9c43] (rev 04) 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] [8086:9c03] (rev 04) 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series SMBus Controller [8086:9c22] (rev 04) 03:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b2] (rev 83) -- 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 #8 from James Rome <jamesrome@alum.mit.edu> --- I got the same issue on my 13.1 I7 server. It is hard-wired into the Ethernet. The Network setup screen pops up, and the "yes" button is unresponsive. It is a Gateway FX machine. -- 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 #9 from James Rome <jamesrome@alum.mit.edu> --- But the install does proceed (using the DVD) if you select "no" -- 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 #10 from Maciej Pilichowski <bluedzins@wp.pl> --- @Stakanov Schufter, Dell Latitude E6500 with wifi connection and custom desktop computer with cable (eth) connection. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening@forge.pr |mfilka@suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972 Jon Harrison <JHarrison@seadog.reno.nv.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |JHarrison@seadog.reno.nv.us --- Comment #11 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- 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" -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mfilka@suse.com |wicked-maintainers@suse.de --- Comment #12 from Michal Filka <mfilka@suse.com> --- (In reply to Jon Harrison from comment #11)
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 <pwieczorkiewicz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pwieczorkiewicz@suse.com Flags| |needinfo?(JHarrison@seadog. | |reno.nv.us) --- Comment #13 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> --- Please provide output of: "hwinfo --network", "journalctl -b -o short-iso" and "ip a" commands. -- 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 #14 from James Rome <jamesrome@alum.mit.edu> --- 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) -- 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 #15 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> --- (In reply to James Rome from comment #14)
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 <JHarrison@seadog.reno.nv.us> --- Created attachment 613059 --> http://bugzilla.opensuse.org/attachment.cgi?id=613059&action=edit hwinfo --network -- 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 #17 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- Created attachment 613060 --> http://bugzilla.opensuse.org/attachment.cgi?id=613060&action=edit putput of "ip a" -- 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 #18 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- Created attachment 613061 --> http://bugzilla.opensuse.org/attachment.cgi?id=613061&action=edit Output of journalctl (no file found) In v13.1 I have a large file for the requested journalctl but nothing when run under v13.2 -- 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 #19 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- Created attachment 613062 --> http://bugzilla.opensuse.org/attachment.cgi?id=613062&action=edit ls output of /etc/sysconfig/network There is no ifcfg-* for the wireless device (which I believe is disabled in the bios) nor for the ethernet card. -- 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 #20 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- Created attachment 613063 --> http://bugzilla.opensuse.org/attachment.cgi?id=613063&action=edit output of "wicked ifstatus p3p2" Using name derived from "ip a" and also shown in the system hardware details of Yast -- 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 <pwieczorkiewicz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|wicked-maintainers@suse.de |yast2-maintainers@suse.de Flags|needinfo?(JHarrison@seadog. | |reno.nv.us) | --- Comment #21 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> --- According to the logs provided the interface name is p3p2 not eth0 and there are no ifcfg configuration files present for any interfaces. Thus after the upgrade network is not configured. Is it configured for NetworkManager rather than wicked? Is NetworkManager running? Nothing for the wicked to be honest. -- 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 <pwieczorkiewicz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wicked-maintainers@suse.de -- 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 #22 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- Just to be clear, I have not completed the upgrade. I aborted, returning to v13.1. I don't want to continue without the connection & repo's and risk needing to restore if I run into a different problem. And I would need to enter the nic settings manually. I was hoping the upgrade would copy the existing settings. I still need to check the kernel command you kindly posted. -- 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 #23 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- Shouldn't the upgrade process create the ifcfg-* files necessary for this to proceed? -- 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 #24 from James Rome <jamesrome@alum.mit.edu> --- Why did 13.2 change the name of the ethernet port? People are expecting to use the old, simple names. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com Assignee|yast2-maintainers@suse.de |mfilka@suse.com -- 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 #25 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> --- (In reply to James Rome from comment #24)
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 <mfilka@suse.com> --- 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. (In reply to James Rome from comment #14)
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 <jamesrome@alum.mit.edu> --- The ifconfig I posted was after I had 13.2 installed. So it has nothing to do with the install process. I poosted it because I suspected that the installer was looking for eth0. -- 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 #28 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- Created attachment 613260 --> http://bugzilla.opensuse.org/attachment.cgi?id=613260&action=edit files in /var/log created while trying to do a DVD update -- 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 #29 from Jon Harrison <JHarrison@seadog.reno.nv.us> --- (In reply to Michal Filka from comment #26)
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 <JHarrison@seadog.reno.nv.us> --- Created attachment 613261 --> http://bugzilla.opensuse.org/attachment.cgi?id=613261&action=edit zip of 2 files changed after creating network connect in VT -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=903972 http://bugzilla.opensuse.org/show_bug.cgi?id=903972#c31 Stakanov Schufter <stakanov@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #31 from Stakanov Schufter <stakanov@freenet.de> --- Either 13.1 or 13.2 are out of support now. If the issue represents with current installations feel free to reopen. Closing this now as I did not encounter the bug with the newest 42.3 install. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com