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
The renaming can be observed by running (w/ an unconfigured/down e1000 nic): rmmod e1000 udevadm monitor -k & modprobe e1000
Ryan, I think we can drop this at least for Fedora 20 http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming http://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceNames
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
I'd target F20+ support for oVirt 3.5, and maybe as a preview in 3.4.
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
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.
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.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.
oVirt 3.5 has been released and should include the fix for this issue.