Results 1 to 7 of 7

Thread: Upgrade Leap 42.3 -> 15.0 Disaster

  1. #1

    Exclamation Upgrade Leap 42.3 -> 15.0 Disaster

    Hi,

    I have just upgraded 2 pcs with Leap 42.3 to 15.0, and both have problem with networking.

    1) PC #1, Linux workstation, networking broke (single static IP ethernet), redefined in yast, now working. Teamviewer 12 stopped working, hanging for forever on launching GUI. Reinstall don’t help.

    2) PC #2, Linux KVM host with 10 ethernet interfaces and 2 VyOS router QEMU instances.

    1 static local IP 192.168.0.172, for management.
    7 ethernet interfaces enslaved for bridges, used by VyOS routers.

    eth0 - 192.168.0.172
    Bridges:
    eth2 - brltc1, eth3 - brbtc1, eth4 - brdmz, eth5 - brint
    eth6 - br_eth6, eth7 - br_eth7, eth8 - br_eth8
    eth1, eth9 - unused

    In Yast (screenshot can't be attached to forum msg for whatever reason), looks like everything is OK, yet it is not.
    Networking messed up completely. Some interfaces, incl. eth0, are simply lost by Wicked.

    Both firewalld and SuSEfirewalll rpms are removed from the system. BTW, I assume SuSEfirewalll should be marked as conflicting with firewalld.

    Is there any way to fix this, or I should wipe out entire OS and install back to 42.03 ?

    Thanks in advance for any help.
    Andrei

    -----------------------

    rthost:/home/andrei # rcnetwork status
    ● wicked.service - wicked managed network interfaces
    Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
    Active: active (exited) since Fri 2018-04-06 13:28:10 EEST; 3min 1s ago
    Process: 2146 ExecReload=/usr/sbin/wicked --systemd ifreload all (code=exited, status=0/SUCCESS)
    Main PID: 725 (code=exited, status=0/SUCCESS)

    Apr 06 13:28:10 rthost.local wicked[725]: eth3 enslaved
    Apr 06 13:28:10 rthost.local wicked[725]: eth6 enslaved
    Apr 06 13:28:10 rthost.local wicked[725]: eth9 setup-in-progress
    Apr 06 13:28:10 rthost.local wicked[725]: br_eth8 up
    Apr 06 13:28:10 rthost.local wicked[725]: brbtc2 up
    Apr 06 13:28:10 rthost.local wicked[725]: br_eth7 up
    Apr 06 13:28:10 rthost.local systemd[1]: Started wicked managed network interfaces.
    Apr 06 13:29:48 rthost.local systemd[1]: Reloading wicked managed network interfaces.
    Apr 06 13:30:18 rthost.local wicked[2146]: eth1 setup-in-progress
    Apr 06 13:30:18 rthost.local systemd[1]: Reloaded wicked managed network interfaces.

    -----------------------

    ping 192.168.0.1
    connect: Network is unreachable

    ———————————
    Brought up eth0

    rthost:/home/andrei # ifup eth0
    eth0 up
    rthost:/home/andrei # ping 192.168.0.1
    PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.639 ms
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.626 ms

    --------------------------

    rthost:/home/andrei # rcnetwork status
    ● wicked.service - wicked managed network interfaces
    Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
    Active: active (exited) since Fri 2018-04-06 13:28:10 EEST; 3min 48s ago
    Process: 2146 ExecReload=/usr/sbin/wicked --systemd ifreload all (code=exited, status=0/SUCCESS)
    Main PID: 725 (code=exited, status=0/SUCCESS)

    Apr 06 13:28:10 rthost.local wicked[725]: eth3 enslaved
    Apr 06 13:28:10 rthost.local wicked[725]: eth6 enslaved
    Apr 06 13:28:10 rthost.local wicked[725]: eth9 setup-in-progress
    Apr 06 13:28:10 rthost.local wicked[725]: br_eth8 up
    Apr 06 13:28:10 rthost.local wicked[725]: brbtc2 up
    Apr 06 13:28:10 rthost.local wicked[725]: br_eth7 up
    Apr 06 13:28:10 rthost.local systemd[1]: Started wicked managed network interfaces.
    Apr 06 13:29:48 rthost.local systemd[1]: Reloading wicked managed network interfaces.
    Apr 06 13:30:18 rthost.local wicked[2146]: eth1 setup-in-progress
    Apr 06 13:30:18 rthost.local systemd[1]: Reloaded wicked managed network interfaces.

  2. #2
    Join Date
    Sep 2010
    Location
    The Netherlands
    Posts
    114

    Default Re: Upgrade Leap 42.3 -> 15.0 Disaster

    Quote Originally Posted by macguru View Post
    Hi,

    I have just upgraded 2 pcs with Leap 42.3 to 15.0, and both have problem with networking.

    networking broke, Teamviewer 12 stopped working, hanging for forever on launching GUI. Reinstall don’t help.
    Networking messed up completely. Some interfaces, incl. eth0, are simply lost by Wicked.


    Both firewalld and SuSEfirewalll rpms are removed from the system.

    Is there any way to fix this?
    Well what did you expect when you upgrade from a stable distro to a distro still in the beta phase?
    Don't want to sound too grumpy, but why not upgrade to tumbleweed wich is designed to have the latest and greatest software?

  3. #3

    Default Re: Upgrade Leap 42.3 -> 15.0 Disaster

    Small update. Problems seems to be with Leap 15 wicked timeouts or lost data which interfaces should be brought up upon system startup.

    "wicked ifup eth0" brings interface up. However, it works till next reboot only.

    Is there any way to fix this ?

  4. #4
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: Upgrade Leap 42.3 -> 15.0 Disaster

    Quote Originally Posted by macguru View Post
    Small update. Problems seems to be with Leap 15 wicked timeouts or lost data which interfaces should be brought up upon system startup.

    "wicked ifup eth0" brings interface up. However, it works till next reboot only.

    Is there any way to fix this ?
    Check the settings in YaST - System - Networksettings. Some renaming of interfaces may have taken place.
    If you rootfs is btrfs, you should be able to boot a previous, pre-upgrade, snapshot.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    29,788

    Default Re: Upgrade Leap 42.3 -> 15.0 Disaster

    Quote Originally Posted by macguru View Post

    In Yast (screenshot can't be attached to forum msg for whatever reason),
    When you want to upload screenshots, you can use http://paste.opensuse.org (at top-right you can choose Image) and post a link in your post.

    And please use the default font for your post. All those bold and whatever all over the post will only distract from the message.

    And while it is nice that you want to test 15.0 before it is released, I am not sure it is wise to install it then on many systems in one move. Install one, test it and when satisfied take another one to see if the hardware is also supported. Just my two cents.
    Last edited by hcvv; 06-Apr-2018 at 08:04.
    Henk van Velden

  6. #6

    Default Re: Upgrade Leap 42.3 -> 15.0 Disaster

    Quote Originally Posted by Knurpht View Post
    Check the settings in YaST - System - Networksettings. Some renaming of interfaces may have taken place.
    If you rootfs is btrfs, you should be able to boot a previous, pre-upgrade, snapshot.
    Nope, interface names are preserved.
    Something wrong how wicked handles startup process.
    I'll be back on Monday and post Wicked config files + /var/log/messages

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: Upgrade Leap 42.3 -> 15.0 Disaster

    Quote Originally Posted by Knurpht View Post
    Check the settings in YaST - System - Networksettings. Some renaming of interfaces may have taken place.
    If you rootfs is btrfs, you should be able to boot a previous, pre-upgrade, snapshot.
    Maybe.
    But,
    I've noticed that on any of my machines that have been upgraded, all previous snapshots are deleted so you can't roll back beyond the last "dup"

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •