-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why net.ifnames=0 is used ? #620
Comments
This will change in Fedora 41: https://fedoraproject.org/wiki/Changes/EnableConsistentDeviceNamingCloud As for the history of the option: I can't really say with absolute certainty, but it was likely added to replicate the official Fedora cloud images. This comment in the change proposal discussion thread links to the oldest surviving instance of the change being introduced in the official Fedora kickstarts. |
Heh, the change proposal you linked says that current Fedora's except cloud use consistent device naming so it seems to confirm that our definitions would be wrong for anything not-cloud? |
Yes, I think the issue started by replicating cloud configs and then it carried over to non-cloud images. |
What I want to do, in preparation of the change (especially for RHEL 9.x in prep for RHEL 10) is to make it configurable. We could detect when the option is added to the blueprint and remove it from the defaults, otherwise use the default for each distro version. |
I digged the git history: I come to this commit (I didn't find a related PR so I open this issue). It seems to be added as an example of customization and then copied from version to version without thinking about it.
2225463#diff-de240f0bca8f03daafeb653ff429aafa12f43b5e0dc8ba327c56108a6ff864f3R70
Original issue is I can't change it:
regen grub config and reinstall kernel-core to trigger dracut regeneration.
The text was updated successfully, but these errors were encountered: