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.
Document URL:
NA ( Not sure where this information should live )
Section Number and Name:
Same as above
Describe the issue:
Looking at this bug https://bugzilla.redhat.com/show_bug.cgi?id=1990875 , We can understand that the success of the Discovery operation depends on whether it will be able to detect and configure the NIC card of client system.
And that depends directly on whether the kernel of Discovery Image has the support of that specific nic driver included or not.
Now, the discovery images upstream are based on CentOS and downstream ones are based on RHEL. There are several RH articles like https://access.redhat.com/solutions/2521021 that document the driver v\s kernel support but without booting from the ISO itself, There is no way we can tell what RHEL\CENTOS release\kernel they are based on.
Suggestions for improvement:
There should be a table present somewhere that documents
Discovery Release | OS Release | Kernel Version | Upstream or Downstream
In that way, even if someone opens a support case for system hardware, where discovery ISO is not able to detect the nic, we may be able to quickly tell why ( in terms of driver support of the kernel ).
Additional information:
NA