Bug 2181158

Summary: Mention the OS Release and kernel base on which a specific version of Discovery ISO was made
Product: Red Hat Satellite Reporter: Sayan Das <saydas>
Component: Discovery ImageAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.12.0CC: lstejska, zuansorg
Target Milestone: UnspecifiedKeywords: Documentation, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 Sayan Das 2023-03-23 08:53:40 UTC 
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
Comment 1 Sayan Das 2023-03-23 09:03:37 UTC 
CC Leos