Description of problem: According to https://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceNames, biosdevname "As part of this feature we also want to remove biosdevname from comps, so that it is not installed anymore for new installations." However, as of F19-TC3, biosdevname is still in place in a minimal install. (Making no changes to network configuration during installation, just accepting defaults.) How reproducible: Install Fedora 19-TC3 from netinstall iso image. Upon reboot, biosdevname package is installed. Actual results: biosdevname is installed Expected results: No biosdevname package.
it is definitely there in comps: [adamw@adam comps (master)]$ git pull Already up-to-date. [adamw@adam comps (master)]$ grep biosdev comps-f19.xml.in <packagereq type="mandatory">biosdevname</packagereq> I could fix this easily but I feel like we'd best get Bill's okay.
The issue here is what we do in anaconda as well - since the initial network configuration happens there, if someone wants to use biosdevname, how does one get it configured in that environment in a way that carries over to the install?
Failing to act on this bz has posed a real problem for F19 GA for me. With the udevd change, and with biosdevname still installed by default (due to comps entry), the ambiguity does interfere with configuring services such as dhcp server. In my case, it was dhcpd.x86_64 (4.2.5-12.fc19) on F19 (beta updated to latest). Out of the box, dhcpd will not start with my previous dcphd.conf (updated to reflect udevd-generated interface name). Jun 27 20:31:45 wallace systemd[1]: Starting DHCPv4 Server Daemon... Jun 27 20:31:45 wallace systemd[1]: Started DHCPv4 Server Daemon. Jun 27 20:31:45 wallace dhcpd: Internet Systems Consortium DHCP Server 4.2.5 Jun 27 20:31:45 wallace dhcpd: Copyright 2004-2013 Internet Systems Consortium. Jun 27 20:31:45 wallace dhcpd: All rights reserved. Jun 27 20:31:45 wallace dhcpd: For info, please visit https://www.isc.org/software/dhcp/ Jun 27 20:31:45 wallace dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in. Jun 27 20:31:45 wallace dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file Jun 27 20:31:45 wallace dhcpd: Wrote 0 deleted host decls to leases file. Jun 27 20:31:45 wallace dhcpd: Wrote 0 new dynamic host decls to leases file. Jun 27 20:31:45 wallace dhcpd: Wrote 0 leases to leases file. Jun 27 20:31:45 wallace dhcpd: Multiple interfaces match the same shared network: enp4s0 p34p1 Jun 27 20:31:45 wallace dhcpd: Error getting hardware address for "enp4s0": No such device Jun 27 20:31:45 wallace dhcpd: Jun 27 20:31:45 wallace dhcpd: This version of ISC DHCP is based on the release available Jun 27 20:31:45 wallace dhcpd: on ftp.isc.org. Features have been added and other changes Jun 27 20:31:45 wallace dhcpd: have been made to the base software release in order to make Jun 27 20:31:45 wallace dhcpd: it work better with this distribution. Jun 27 20:31:45 wallace dhcpd: Jun 27 20:31:45 wallace dhcpd: Please report for this software via the Red Hat Bugzilla site: Jun 27 20:31:45 wallace dhcpd: http://bugzilla.redhat.com Jun 27 20:31:45 wallace dhcpd: Jun 27 20:31:45 wallace dhcpd: exiting. Jun 27 20:31:45 wallace systemd[1]: dhcpd.service: main process exited, code=exited, status=1/FAILURE Jun 27 20:31:45 wallace systemd[1]: Unit dhcpd.service entered failed state. I removed the biosdevname package, and cleared the wired lan network devintion (via settings, reset), rebooted, redefined the wired lan with the required static information, then was able to successfully start dhcpd. Jun 27 21:15:38 wallace dhcpd: Internet Systems Consortium DHCP Server 4.2.5 Jun 27 21:15:38 wallace dhcpd: Copyright 2004-2013 Internet Systems Consortium. Jun 27 21:15:38 wallace dhcpd: All rights reserved. Jun 27 21:15:38 wallace dhcpd: For info, please visit https://www.isc.org/software/dhcp/ Jun 27 21:15:38 wallace dhcpd: WARNING: Host declarations are global. They are not limited to the scope you declared them in. Jun 27 21:15:38 wallace dhcpd: Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file Jun 27 21:15:38 wallace systemd[1]: Started OpenSSH server daemon. Jun 27 21:15:38 wallace systemd[1]: Started Sendmail Mail Transport Agent. Jun 27 21:15:38 wallace libvirtd[1800]: libvirt version: 1.0.5.2, package: 1.fc19 (Fedora Project, 2013-06-12-22:00:57, buildvm-12.phx2.fedoraproject.org) Jun 27 21:15:38 wallace dhcpd: Wrote 0 deleted host decls to leases file. Jun 27 21:15:38 wallace dhcpd: Wrote 0 new dynamic host decls to leases file. Jun 27 21:15:38 wallace dhcpd: Wrote 0 leases to leases file. Jun 27 21:15:38 wallace libvirtd[1800]: open("/var/run/libvirt/network/nwfilter.ltmp"): No such file or directory Jun 27 21:15:38 wallace dhcpd: enp4s0 missing an interface address Jun 27 21:15:38 wallace systemd[1]: Failed to read PID from file /run/sm-client.pid: Invalid argument Jun 27 21:15:38 wallace systemd[1]: Started Sendmail Mail Transport Client. Jun 27 21:15:38 wallace systemd[1]: Starting Multi-User System. Jun 27 21:15:38 wallace systemd[1]: Reached target Multi-User System. Jun 27 21:15:38 wallace systemd[1]: Starting Graphical Interface. Jun 27 21:15:38 wallace systemd[1]: Reached target Graphical Interface. Jun 27 21:15:38 wallace systemd[1]: Starting Update UTMP about System Runlevel Changes... Jun 27 21:15:38 wallace systemd[1]: Starting Stop Read-Ahead Data Collection 10s After Completed Startup. Jun 27 21:15:38 wallace systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup. Jun 27 21:15:38 wallace dhcpd: Listening on LPF/enp4s0/50:46:5d:0a:81:72/192.168.1.0/24 Jun 27 21:15:38 wallace dhcpd: Sending on LPF/enp4s0/50:46:5d:0a:81:72/192.168.1.0/24 Jun 27 21:15:38 wallace dhcpd: Sending on Socket/fallback/fallback-net
If it's a big deal, then just take biosdevname out of your package set with a kickstart?
And if people are worried about something before release, I really wish they'd let us know *before* release. If you really wanted something done about this, you know, ask. The bug just sat there for two months. It's a bit late to do anything now.
Bill: do we really want to let people configure biosdevname during install? I thought we were only keeping it around for existing installs that want to keep using it. Letting people 'choose' between two incompatible device naming schemes in the installer is exactly the kind of 'choice' that's terrible. I'd say we should just ditch it in comps and be done.
Adam - your question may be answered in bug 965718.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
We dealt with this (a bit belatedly) for f21. *** This bug has been marked as a duplicate of bug 965718 ***