Bug 910701

Summary:	Remove persistent-net-naming hack
Product:	[Retired] oVirt	Reporter:	Fabian Deutsch <fdeutsch>
Component:	ovirt-node	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	bugs, fdeutsch, hadong, iheim, jboggs, leiwang, mgoldboi, ovirt-bugs, ovirt-maint, rbalakri
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	node
Fixed In Version:	2.7.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:23:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1094719

Description Fabian Deutsch 2013-02-13 10:36:32 UTC

Description of problem:
Previously we carried aroudn our own persistent net naming solution which we needed because of the special circumstances with our r/o rootfs.

sysd-v197 brings a new feature to consistently name net devices (but not virtio ones) [0]
v197 is already part of our 2.6.0 release.

But this feature will only be actiavte if this rules [1] file is present (currently not the case)

We should remove our solution in favor of this upstream solution as soon as possible.

[0] http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
[1] http://cgit.freedesktop.org/systemd/systemd/tree/rules/80-net-name-slot.rules

Comment 1 Fabian Deutsch 2013-02-13 10:38:51 UTC

The renaming can be observed by running (w/ an unconfigured/down e1000 nic):

rmmod e1000

udevadm monitor -k &
modprobe e1000

Comment 2 Fabian Deutsch 2013-11-28 13:15:14 UTC

Ryan,

I think we can drop this at least for Fedora 20

http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming
http://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceNames

Comment 3 Sandro Bonazzola 2014-03-04 09:20:18 UTC

This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.

Comment 4 Fabian Deutsch 2014-04-30 12:17:44 UTC

I'd target F20+ support for oVirt 3.5, and maybe as a preview in 3.4.

Comment 5 Sandro Bonazzola 2014-05-08 13:50:47 UTC

This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.4.2 as it has priority high, please retarget if needed.
If this is a blocker please add it to the tracker Bug #1095370

Comment 6 Sandro Bonazzola 2014-06-11 07:05:03 UTC

This is an automated message:
oVirt 3.4.2 has been released.
This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.

Comment 7 Sandro Bonazzola 2014-06-11 07:05:37 UTC

This is an automated message:
oVirt 3.4.2 has been released.
This bug has been re-targeted from 3.4.2 to 3.4.3 since priority or severity were high or urgent.

Comment 8 Sandro Bonazzola 2014-07-18 09:43:14 UTC

This is an automated message.
oVirt 3.4.3 has been released while this bug was still open.
The bug has been re-targeted to 3.4.4 accordingly.

Comment 9 Itamar Heim 2014-08-10 20:30:02 UTC

Closing old bugs. If this issue is still relevant/important in current
version, please re-open the bug.

Comment 10 Sandro Bonazzola 2014-10-17 12:23:12 UTC

oVirt 3.5 has been released and should include the fix for this issue.