[Bug 1550539] Re: VMWare network interface name change with xenial upgrade

[Martin Pitt]

I installed VMWare player and compared a wily and a xenial installation.
On xenial I indeed get "ens33", while on wily I get a rather bad name
"eno16777736". You did not mention the old name of the ethernet
interface, but can you confirm that this was a wily *install* (as
opposed to an upgrade from an earlier release), and that the old name
was *not* eth0, but "eno16777736" or similar? Then indeed the migration
to ifnames does not apply as wily already used ifnames.

This naming was fixed in
https://github.com/systemd/systemd/commit/6c1e69f9 by ignoring interface
indexes that the BIOS reported that are implausibly high (as VMWare does
that for some reason).

We do know the slot-based names that are being used since the above
commit so we could attempt to auto-fix at least /etc/network/interfaces
in postinst. However, we can't fix possible other places where the
previous name is being used, so perhaps the safest approach would be to
document this in the release notes and in NEWS.

** Summary changed:

- VMWare network interface name change with xenial upgrade
+ VMWare network interface name change with wily → xenial upgrade

** Changed in: systemd (Ubuntu)
       Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Importance: High => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1550539

Title:
  VMWare network interface name change with wily → xenial upgrade

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I just (2016-02-26) upgraded from wily to xenial in my VMWare VM. The
  network interface name changed but the upgrade process didn't change
  /etc/network/interfaces. As such I was left without networking. This
  may be related to bug #1473542, but obviously isn't the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2
  Uname: Linux 4.4.0-7-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Feb 26 16:54:47 2016
  InstallationDate: Installed on 2015-10-29 (120 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic root=UUID=9b4f66d9-95e1-45ff-b167-8ce887475c7e ro elevator=noop
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-02-26 (0 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1550539/+subscriptions