Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1740199

Summary: When deploying the RHCOS OVA - it is tagged as "Other 2.6.x Linux".
Product: OpenShift Container Platform Reporter: David Hernández Fernández <dahernan>
Component: RHCOSAssignee: Steve Milner <smilner>
Status: CLOSED DUPLICATE QA Contact: Micah Abbott <miabbott>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.1.zCC: bbreard, dustymabe, imcleod, jligon, nstielau
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-12 13:35:47 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:
Attachments:
Description Flags
Example of the summary. none

Description David Hernández Fernández 2019-08-12 13:06:48 UTC 
Created attachment 1602931 [details]
Example of the summary.

Description of problem:
When deploying the RHCOS OVA - it comes up tagged as "Other 2.6.x Linux" instead of RHEL or RHCOS.

Version-Release number of selected component (if applicable):
Using the following OVA for 4.1z
 - https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.1/latest/	         
 - rhcos-4.1.0-x86_64-vmware.ova	

Steps to Reproduce:
1. Do not choose "Operative System tag" under VMWare when deploying.
2. Deploy the OVA for VMWare UPI OCP4.1 Installer
3. Check Summary of the VM.

Actual results: RHCOS is not detected, instead, it shows "Other 2.6.x Linux"

Expected results: Displayed as "Red Hat Entreprise Linux 8" or "RHCOS".

Additional info: Probably is not an issue of RHCOS OVA but from VMWare instead.
Comment 2 Micah Abbott 2019-08-12 13:35:47 UTC 
This is a duplicate of RHBZ#1712960

The fix is in place, however we have yet to release updated 4.1 boot images.

*** This bug has been marked as a duplicate of bug 1712960 ***