Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1595068

Summary: Foreman fact parser unable to process NPAR NICs with underscore which breaks discovery
Product: Red Hat Satellite Reporter: vijsingh
Component: Discovery PluginAssignee: Lukas Zapletal <lzap>
Status: CLOSED WONTFIX QA Contact: Jitendra Yejare <jyejare>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3.2CC: lzap, rabajaj
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: https://projects.theforeman.org/issues/24073
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-03 16:29:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description vijsingh 2018-06-26 03:27:40 UTC 
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
Comment 1 vijsingh 2018-06-26 03:30:53 UTC 
As a workaround use below kernel parameters during discovery in order to disable new naming scheme:

 "biosdevname=0"
Comment 2 Lukas Zapletal 2018-06-26 08:42:56 UTC 
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.
Comment 5 Bryan Kearney 2020-01-15 21:00:48 UTC 
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.
Comment 6 Bryan Kearney 2020-02-03 16:29:52 UTC 
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.