Bug 878035

Summary:	Unique predictable iface names changed
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Michal Hrusecky <mhrusecky>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED UPSTREAM	QA Contact:	systemd maintainers <systemd-maintainers>
Severity:	Normal
Priority:	P5 - None	CC:	duwe, mpluskal, rmilasan, tchvatal, trenn
Version:	13.2 Milestone 0
Target Milestone:	---
Hardware:	Other
OS:	Other
URL:	https://bugs.freedesktop.org/show_bug.cgi?id=78736
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michal Hrusecky 2014-05-15 11:30:43 UTC

I did upgrade on my machine that runs Factory and I got no network. After some digging around, I found out that my unique predictable interface name changed from eno1 to em1. I thought that the whole point of abandoning eth0 was to make sure that the device names are predictable and don't change...

My network card is Intel Corporation 82579LM Gigabit Network Connection.

Comment 1 Dr. Werner Fink 2014-05-15 11:34:14 UTC

This is it is: report this upstream if you thnik this is a bug.

Comment 2 Martin Pluskal 2014-05-15 11:41:18 UTC

Afaik this is caused by installation of biosdevname, without biosdevname interfaces on one of my test machines are eno1 and eno2, but with biosdevname:
# biosdevname -i eno1
em1

Comment 3 Michal Hrusecky 2014-05-15 11:42:41 UTC

Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=78736

Comment 4 Dr. Werner Fink 2014-05-15 12:03:11 UTC

(In reply to comment #2)

This seems to be a problem of biosdevname and not systemd/udevd ... IMHO you should not mix them or use the script /usr/lib/udev/udev-generate-peristent-rule to generate a renaming udev rule.

Comment 5 Robert Milasan 2014-05-15 12:08:40 UTC

It will never work properly, because both 80-net-setup-link.rules and 71-biosdevnames.rules are not checking for KERNEL='...', they have been dropped and well we have the issue now.

I honestly believe in both rules there should be a check:

KERNEL=="eth*|wlan*|wwan*", ....

We already had a bug for biosdevnames, but in the bug I mentioned this and nobody cared :).

Comment 6 Dr. Werner Fink 2014-05-15 12:18:11 UTC

(In reply to comment #5)

Does this mean that this is a bug for biosdevnames?  Do we have this package on SLES-12 as well?

Comment 7 Martin Pluskal 2014-05-15 12:23:39 UTC

(In reply to comment #6)
> (In reply to comment #5)
> 
> Does this mean that this is a bug for biosdevnames?  Do we have this package on
> SLES-12 as well?

We do -  see also bnc#876733. It is my understanding that this issue was triggered by installation of biosdevname during update/upgrade.

Comment 8 Robert Milasan 2014-05-15 12:49:56 UTC

No, no bug in biosdevname, just a way to fix biosdevname. The fix was upstream: http://linux.dell.com/cgi-bin/cgit.cgi/biosdevname.git/commit/?id=6f7fbcc352aeae08b5cf2a8e608f92abf98529f8

Seems that they have dropped KERNEL option because systemd doesn't have KERNEL option.

Normally, I would go with both having KERNEL option as it will only rename the interfaces which were named by the kernel, usually eth*,wlan*,wwan*, but this doesn't apply anymore in eider of them.

It's not a bug, but its a bug, depends on what u expect. The user can always drop biosdevname or use at boot biosdevname=0 or net.ifnames=0 to disable the udev renaming.