Description of problem: Discovery host fails with error 'Unable to assign subnet, primary interface is missing IP address' for Dell Blades where NICs naming contains "_"(underscore) in it e.g. nics naming em1_1,em1_2 Version-Release number of selected component (if applicable): Satellite 6.3.2 foreman-discovery-image 3.4.4-1 How reproducible: Always Steps to Reproduce: 1. Boot Dell blade with Foreman-discovery ISO PXE-Less/PXE. 2. Select any NIC to select Primary interface. 3. You see below error on Screen: "ERROR -- : Discovery failed, code 422, reason: ERF42-1064 [Foreman::Exception]: Unable to assign subnet, primary interface is missing IP address" 4. Below comes under '/var/log/foreman/production.log' NICs: "interfaces"=>"em1_1,em1_2,em2_1,em2_2,em3_1,em3_2,em4_1,em4_2,lo", Error: "Completed 422 Unprocessable Entity in 497ms (Views: 0.2ms | ActiveRecord: 74.6ms)" Actual results: "ERROR -- : Discovery failed, code 422, reason: ERF42-1064 [Foreman::Exception]: Unable to assign subnet, primary interface is missing IP address" Expected results: Satellite should be able to handle the NICs naming which contain the "_" underscore in it Additional info: Dell NPAR naming scheme cannot be discovered: https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf
As a workaround use below kernel parameters during discovery in order to disable new naming scheme: "biosdevname=0"
This is new bug we had no idea about. https://community.theforeman.org/t/dell-naming-scheme-for-npar-nics/10136/2 For the moment only workaround can help, we need to rewrite NIC parsing bits. Might be more complex change due to how facter reports bonds/vlans.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.