https://bugzilla.redhat.com/show_bug.cgi?id=2051874
--- Comment #11 from Yu Watanabe <yuwatana(a)redhat.com> ---
IIUC,
- both commands rename_device and ifcfg-devname handle ifcfg files and extract
matching interface name.
- if a matching ifcfg file exists, then interface renaming through .link files
needs to be disabled.
- so, 60-net.rules file set NAME=.
That's OK, as it does not conflict any other tools unless a user creates ifcfg
files explicitly.
However,
- the commands also handle 'ifname=' kernel command line option.
That's problematic and confuses users, even if rename_device previously did so.
As already pointed out by Zbigniew in the above, systemd-network-generator
produces .link files
from 'ifname=' and other command line options. If ifcfg-devname (or
rename_device) is installed,
then systemd-network-generator.service does not work as expected, even if the
service is enabled
and no ifcfg files exist.
At least, it makes harder to debug if an issue related to 'ifname=' handling
occurs.
We (unfortunately) still support ifcfg files, but that is mostly compatibility
reason, I think.
So, functionalities not related to ifcfg files should be dropped from the code.
--
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2051874