Bug 1347268

Summary:	When creating Compute Profile in Satellite 6.1.x, "Virtual H/W version" not listed for VMware vSphere 6 Compute Resource
Product:	Red Hat Satellite	Reporter:	Nagoor Shaik <nshaik>
Component:	Compute Resources	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Daniel Lobato Garcia <dlobatog>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1.8	CC:	bbuckingham, dlobatog, ehelms, jcallaha, mhulan
Target Milestone:	Unspecified
Target Release:	Unused
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:	2018-02-21 16:51:07 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 Nagoor Shaik 2016-06-16 12:15:24 UTC

Description of problem:
Latest Virtual H/W version i.e 11 is not listed for VSphere 6.0 Compute Resource while creating Compute Profile in Satellite 6.1.x

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

VMware vSphere 6 environment

How reproducible:
100%

Steps to Reproduce:

1. Try creating a Compute Profile on Satellite Server v.6.1.x with VMware Vsphere v.6.0

2. While selecting the Virtual Hardware version option, it doesn't the latest H/w version only HW 10 and below listed.

Actual results:

Latest Virtual H/W version i.e 11 is not listed for VSphere 6.0 Compute Resource while creating Compute Profile in Satellite 6.1.x

Expected results:

Virtual H/W version should be refreshed from the vSphere environment

Additional info:

Comment 4 Daniel Lobato Garcia 2017-08-30 09:19:20 UTC

Verified.

Version tested: Satellite 6.3 snap 13

Just by checking in the console (foreman-rake console) we can see all available HW versions for VMWare. Definitely 10 is included as asked originally in this BZ.

irb(main):021:0> Foreman::Model::Vmware.new.vm_hw_versions
.vm_hw_versions
=> {"Default"=>"Default", "vmx-13"=>"13 (ESXi 6.5)", "vmx-11"=>"11 (ESXi 6.0)", "vmx-10"=>"10 (ESXi 5.5)", "vmx-09"=>"9 (ESXi 5.1)", "vmx-08"=>"8 (ESXi 5.0)", "vmx-07"=>"7 (ESX/ESXi 4.x)", "vmx-04"=>"4 (ESX/ESXi 3.5)"}
`

Comment 5 Satellite Program 2018-02-21 16:51:07 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-2018:0336