18th Jan 2021 by Müller, Sabrina

OTC BMS upgrade from Ubuntu 16.04 to 18.04

needs special attention to the network configuration. <h2>Background, what happens with the network?</h2> Since Ubuntu 17.04 the new default network configuration method for network devices is 'netplan'. (More information: https://netplan.io/). The default nework configuration in Ubuntu 16.04 instead, based on ifupdown and /etc/network/interfaces. These are different tools to configure network stuff with diefferen configuration files and syntax. If you upgrade a running Ubuntu 16.04 VM to Ubuntu 18.04, your network configuration will NOT automatically migrated. Without manual interaction after an distribution ubgrade was done, rebooting the BMS vm will result in loosing your network access, as the the vm now try to load a non existing netplan configuration. You need to greate a valid netplan configuration first. To fix this issue: <ul> <li>after dist upgrade successfully finished </li> <li>but BEFORE the final reboot: </li> </ul> => generate a valid netplan configuration You can do that manually or by using OTC tool bms-network-setup to configure network interfaces on OTC BMS. Using OTC tool bms-network-setup will not migrate you configuration, but create a new one, same way as the first boot of an BMS vm. If you did own changes in your network cofiguration you should migrate your configuration manually. <h2>Example to upgrade from Ubuntu 16.04 to 18.04</h2> Prepare BMS VM <pre><code>$ sudo apt update $ sudo apt upgrade -y # keep all configs original $ sudo apt dist-upgrade -y $ sudo apt autoremove $ sudo reboot </code></pre> Ubuntu way to upgrade to 18.04 <pre><code>$ cat /etc/os-release | grep ^VERSION= VERSION="16.04.7 LTS (Xenial Xerus)" $ sudo apt install update-manager-core $ sudo apt autoremove -y $ sudo do-release-upgrade </code></pre> follow the upgrade process until 'System upgrade is complete.' <pre><code>(...) System upgrade is complete. Restart required To finish the upgrade, a restart is required. If you select 'y' the system will be restarted. Continue [yN] N =>** ! Press N (no reboot) ** </code></pre> Now create a valid netplan network configuration. You can do it manually, or use a OTC script bms-network-setup.sh used to configure BMS network interfaces for Ubuntu 18.04. <ul> <li> <div class="notices yellow"> This script will override your network configration same as your VMs first boot after creating. </div> </li> <li> <div class="notices yellow"> In case you changed your network configuration manually your manually changes will get lost when loosing the tool. </div> </li> <li> <div class="notices yellow"> In this case, we recommend to configre neplan configuration manually. </div> </li> </ul> For more information to netplan: [https://netplan.io] <h1>create new netplan configuration with OTC script</h1> <pre><code>$ /opt/otc/bms-setup/bms-setup.sh Dev 2c:55:d3:c4:9d:a1: eth0->eth0 Dev 2c:55:d3:c4:9d:a2: eth1->eth1 Set up bonding: {'bond0': ['eth0', 'eth1']} Created symlink /etc/systemd/system/systemd-networkd-wait-online.service.wants/bms-network-setup.service → /usr/lib/systemd/system/bms-network-setup.service. </code></pre> New netplan configration files were created <pre><code>$ ls -l /etc/netplan/ total 12 -rw-r--r-- 1 root root 207 Jan 11 10:51 60-ifcfg-eth0.yaml -rw-r--r-- 1 root root 207 Jan 11 10:51 60-ifcfg-eth1.yaml -rw-r--r-- 1 root root 310 Jan 11 10:51 61-ifcfg-bond0.yaml </code></pre> To double check the synax <pre><code>$ netplan apply </code></pre> If there are not error, reboot no <pre><code>> $ reboot</code></pre> After reboot, check again: <pre><code>$ cat /etc/os-release | grep ^VERSION= VERSION="18.04.5 LTS (Bionic Beaver)" </code></pre> Migration successfully finished now.