← Back to team overview

touch-packages team mailing list archive

[Bug 1315218] Re: renaming net interfaces sometimes gives "renameX" names

 

When using the old-style /etc/udev/rules.d/70-persistent-net.rules
schema this is an unavoidable race condition. Our udev package has a
patch to try and make the best of it
(http://anonscm.debian.org/gitweb/?p=pkg-
systemd/systemd.git;a=blob;f=debian/patches/Revert-udev-network-device-
renaming-immediately-give.patch) but it can only help so far.

Since Ubuntu 15.10 we use a different schema for persistent names which
entirely avoids this race condition. So if this still happens, I suggest
removing 70-persistent-net.rules and adjusting your configuration to the
new schema, as documented in /usr/share/doc/udev/README.Debian.gz .

** Changed in: systemd (Ubuntu)
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1315218

Title:
  renaming net interfaces sometimes gives "renameX" names

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I have been having problems, and some others have to, with 14.04
  devbiosname causing renaming of network interfaces.

  I also started to have this issue today on 12.04

  In both cases ethx gets renamed to renamey interface, and causes the
  interface to basically get lost.

  In my 12.04 case, I started with two nics, eth0 and eth1, then added a
  third as eth2, and removed eth0 from the system.

  This caused eth0 to be renamed to eth1, and eth1 to be renamed to
  eth2.

  Just now, this started failing, and eth0 gets renamed to rename3, and
  eth1 stays as eth1. and boot fails due to no network.

  for 14.04, the same type of issue, eth0 gets renamed to rename2, and
  eth1 gets renamed to whatever it should (em2, p5p1, ...)

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