http://bugzilla.opensuse.org/show_bug.cgi?id=1095383
http://bugzilla.opensuse.org/show_bug.cgi?id=1095383#c9
Thomas Formella
(In reply to Thomas Formella from comment #6)
(In reply to Michal Filka from comment #5)
(In reply to Thomas Formella from comment #0)
I'm trying to upgrade a working Leap 42.3 to Leap 15.0 with the "openSUSE-Leap-15.0-NET-x86_64267" ISO image. Network connection is via wired ethernet. Previous upgrades, for example from 42.2 > 42.3, worked flawlessly.
Boot parameter: ipv4only=1
All I can see is:
Loading basic drivers... ok ... Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet drivers: r8169* eth0: network config created Sending DHCP4 request to eth0... DHCP configuration failed.
Omitting the "ipv4only=1" boot parameter leads to the same result (the router is IPv4 only).
Could you pls switch to terminal and attach output of
journalctl -b -o short-iso | fgrep wicked
Thanks.
tty1:install:/# journalctl -b -o short-iso | fgrep wicked bash fgrep: command not found
tty1:install:/# journalctl -b -o short-iso | grep wicked bash journalctl: command not found
tty1:install:/# journalctl bash journalctl: command not found
Sorry, any other way to gather the informations?
ah sorry we're in installer ... So, could you pls attach /var/log/wickedd.log ? Thx
As a side note, I'd bet that it is a problem with resolving DHCP request.
After an ifdown eth0 && ifup eth0, the DHCP request suddenly worked, but for a short time only. I ran the netinstaller, which upgraded Leap 42.3 to Leap 15.0, but after the first automatic reboot the DHCP configuration failed again. As I urgently needed my machine for other work, I followed a advise found somewhere in a forum (the subject was about wicked/DHCP leases/UUID): I switched to NetworkManager via YaST (eth0 immediately came up with the correct DHCP configuration) and then back to wicked. Since then, wicked works as expected, even after several reboots. I'm sorry that I wasn't able to post more details, the problem is solved and the bug can be closed. -- You are receiving this mail because: You are on the CC list for the bug.