Bug 2269507

Summary:	Update for VMWare Hardware version 20 and 21 needed for VMware 8
Product:	Red Hat Satellite	Reporter:	sganar
Component:	Compute Resources - VMWare	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	sganar
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.15.0	CC:	ahumbe, chrobert, gtalreja, lstejska, mhulan, rlavi
Target Milestone:	stream	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 17: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:

Description sganar 2024-03-14 09:03:57 UTC

Description of problem:
No vm hardware version 20 and 21 is present which is needed for VMware 8 provisioning

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

How reproducible:
Always

Steps to Reproduce:
1. Create a VMware compute resource with vCenter 8
2. Try to select vm hardware version 20 or 21

Actual results:
vm hardware version 20 or 21 missing.

Expected results:
vm hardware version 20 or 21 should be present 

Additional info:
There is already a issue created -> https://community.theforeman.org/t/update-for-vmware-hardware-version/37242 and the coresponding PR for the fix as well -> https://github.com/theforeman/foreman/pull/10090/files

Comment 1 sganar 2024-03-14 09:19:14 UTC

PR for the fix has been merged, moving it to POST

Comment 2 sganar 2024-04-29 13:55:27 UTC

Verified.

Tested on Satellite Stream Snap 56.0

Steps followed: 
1. Create a VMware compute resource with vCenter 8
2. Try to select vm hardware version 20 or 21

Observation:
vm hardware version 20 or 21 is displayed now

Comment 3 Eric Helms 2024-06-06 17:26:00 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.