Bug 1758645

Summary: Virtual H/W version for VMware 6.7 are missing
Product: Red Hat Satellite Reporter: roarora
Component: Compute Resources - VMWareAssignee: Ondřej Ezr <oezr>
Status: CLOSED ERRATA QA Contact: Sanket Jagtap <sjagtap>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: bkearney, chrobert, mawerner, mhulan, oezr, pcreech, sjagtap, spetrosi
Target Milestone: 6.7.0Keywords: EasyFix, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
You cannot provision a VMWare virtual machine with the ESXi 6.7 U2 hardware version from Satellite.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-14 13:26:00 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
Hardware versions vmware none

Description roarora 2019-10-04 17:21:09 UTC 
Description of problem:

While creating  a VM or in compute profile, Virtual H/W version options for VMware 6.7 are missing ,

Available list is 
13 (ESXi 6.5)
11 (ESXi 6.0)
10 (ESXi 5.5)
9 (ESXi 5.1)
8 (ESXi 5.0)
7 (ESX/ESXi 4.x)
4 (ESX/ESXi 3.5)

VMware 6.7 options are added in upstream in following commit but are missing in satellite
https://github.com/theforeman/foreman/commit/fc3d76eff6


Version-Release number of selected component (if applicable):
6.5

How reproducible:
Always

Expected results:
VMware 6.7 options should be listed
Comment 3 Ondřej Ezr 2019-10-04 17:55:19 UTC 
This is resolved in upstream already, linking the GitHub PR and upstream issue.
Comment 6 Sanket Jagtap 2020-01-20 13:30:44 UTC 
Build: Satellite 6.7 Snap9 


The Virtual H/W version field is present and has correct options. PFA
Comment 7 Sanket Jagtap 2020-01-20 13:32:00 UTC 
Created attachment 1653956 [details]
Hardware versions vmware
Comment 11 errata-xmlrpc 2020-04-14 13:26:00 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1454