Bug #16526
closed
Package biosdevname is missing on the discovery image
Description
You don't have biosdevname installed on the Foreman Discovery image and we do on the OS.
With consistent network names enabled and biosdevname installed and enabled I get em1.
With consistent network names enabled and biosdevnames=0 or the biosdevname package uninstalled I get eno1.
My initial instinct is that biosdevname should be on the discovery image and if people want to disable biosdevname then they can do biosdevname on the APPEND line for discovery in /var/lib/tftpboot/pxelinux.cfg/default and either not install it or set biosdevname=0 in grub via their kickstart, especially since the Satellite Kickstart Default ks installed biosdevname as part of @Core so people are basically condemned to this behavior by default.
Updated by Lukas Zapletal over 7 years ago
To test this feature, you need a DELL system and explicitly enable this feature via kernel command line.
Note that unless the system is a Dell system, or biosdevname is explicitly enabled as described in Section 8.6.2, “Enabling and Disabling the Feature”, the systemd naming scheme will take precedence.
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-discovery-image/pull/81 added
Updated by Lukas Zapletal over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman-discovery-image|ceaef2ab8527174a4a7e2d4405449f0979548c2b.
Updated by Lukas Zapletal over 7 years ago
QA notes: DELL systems have different naming conventions of network cards, but this only works when biosdevname package is present on the image. We install it by default on provisioned systems, so FDI has it too now.
To verify provision a system with default discovery options and default PXELinux/Kickstart templates (without any changes). The network card name on discovered node should be named same as on the provisioned system.