Upgraded a 43.3 system (running under VMWare) to kernel-default-4.4.132-53.

After restart, the system was not reachable on the network, which was obviously
a major problem and customer was angry.

The problem is that, while the eth0 was present and visible in "ifconfig -a",
it was not configured with an IP address.

Turns out this was because wicked decided eth0 was "device-unconfigured",
whatever that means (WTF does that mean??)

  May 24 20:29:50 test systemd[1]: Starting wicked managed network
interfaces...
  May 24 20:30:20 test wicked[729]: lo              up
  May 24 20:30:20 test wicked[729]: eth0            device-unconfigured

After jumping through the hoops necessary to get console access, I was able to
manually configure the interface and set a default route and everything worked
again... until the next reboot... which I'm too afraid to attempt at this
point.

Nothing else much changed with the latest update other than the kernel upgrade
(previously was 4.4.126-48.2).