Red Hat Bugzilla – Bug 1023609
'biosdevname=0' not passed into installed system
Last modified: 2013-11-23 22:59:48 EST
If you run the installer with 'biosdevname=0', it respects this setting: biosdevname is not active, and you get systemd persistent naming names for your network devices (https://fedoraproject.org/wiki/Features/SystemdPredictableNetworkInterfaceNames ). But the parameter is not passed into the installed system, so when you boot the installed system, biosdevname *is* active, and you get biosdevname names for your network devices instead - you have to know to manually edit the grub config file to add biosdevname=0 there too. It was noted during the F19 cycle that this inconsistency (which you got baked into F19, for free!) can cause various undesirable effects, so ideally we should keep things consistent, here.
Discussed in 2013-11-14 Blocker Review Meeting . This was voted a AcceptedFreezeException. This setting should be consistent in the installer environment and in the installed system. We would accept a patch after freeze if self-contained and safe.
The patch is safe.
anaconda-20.25.8-1.fc20 has been submitted as an update for Fedora 20.
Package anaconda-20.25.8-1.fc20, pykickstart-1.99.46-1.fc20, python-blivet-0.23.5-1.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-20.25.8-1.fc20 pykickstart-1.99.46-1.fc20 python-blivet-0.23.5-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Does it set "biosdevname=1" also?
Yes, no matter what the value of the installer biosdevname boot option is, it is just passing it if it founds any.
pykickstart-1.99.46-1.fc20, python-blivet-0.23.5-1.fc20, anaconda-20.25.9-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.