Observations on upgrading 12.3 to 13.1 on VMWare ESX / vSphere

Not sure where to put this but let’s put it here for posterity and in case people run into same issues.

I have a number of 12.3’s running on vSphere/ESX environment and I was doing some test upgrades on some of the less important boxes, these are some of the things I ran into:

  1. After upgrading the system and successfully rebooting, eth0 vanished and 82545EM Gigabit Ethernet Controller (Copper) (eth0) was replaced with an ens32 driver provided Ethernet card whereas the old card was renamed to Gigabit Ethernet Something Something Dark Side - simple fix was to delete the old card and re-configure the new one, replacing ens32 with eth0 as the device name (broke all my scripts since I use eth0 explicitly which somewhat annoyed me, not much but a little)

  2. For some obscure and I cannot fathom why reason 13.1 decided that my MariaDB installations were a poor choice and replaced them all with MySQL-Community-Server, naturally this caused complete havoc because it was trying to upgrade a 5.5 db to 5.6 and well, that doesn’t quite work out so well - luckily I was able to replace it with MariaDB after installation. I doubt this has anything to do with the virtualization environment but rather some dependency when upgrading.

  3. My old Apache installations blew up, required removing some old directives from /etc/apache2/default-server.conf, mainly some old manual? remnants.

Apart from those I have yet to see other issues pop up - running on vSphere 5.1 and 5.5 mainly.
Mind you I used the ever so wonderful and trustworthy; sed -i ‘s/12.3/13.1/g’ /etc/zypp/repos.d/ && zypper dup -l* to upgrade the boxes. Yeah yeah, I know… rotfl!

On Tue 19 Nov 2013 10:56:01 PM CST, Miuku wrote:

  1. After upgrading the system and successfully rebooting, eth0 vanished
    and 82545EM Gigabit Ethernet Controller (Copper) (eth0) was replaced
    with an ens32 driver provided Ethernet card whereas the old card was
    renamed to Gigabit Ethernet Something Something Dark Side - simple fix
    was to delete the old card and re-configure the new one, replacing ens32
    with eth0 as the device name (broke all my scripts since I use eth0
    explicitly which somewhat annoyed me, not much but a little)

Hi
A known change to align with:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/


Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLED 11 SP3 (x86_64) GNOME 2.28.0 Kernel 3.0.93-0.8-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!