[Bug 1315218] Re: persistant network naming and devbiosname concurrency issue
Launchpad Bug Tracker
1315218 at bugs.launchpad.net
Mon May 26 12:24:28 UTC 2014
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
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/1315218
Title:
persistant network naming and devbiosname concurrency issue
Status in “systemd” package in Ubuntu:
Confirmed
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
More information about the foundations-bugs
mailing list