This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2269507 - Update for VMWare Hardware version 20 and 21 needed for VMware 8
Summary: Update for VMWare Hardware version 20 and 21 needed for VMware 8
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.15.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: stream
Assignee: satellite6-bugs
QA Contact: sganar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-14 09:03 UTC by sganar
Modified: 2024-06-06 17:26 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:26:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 37244 0 Normal Closed Hardware versions for VMWare VSphere 8.0 and 8.0U2 are missing 2024-03-14 09:03:57 UTC
Red Hat Issue Tracker   SAT-23957 0 None Migrated None 2024-06-06 17:25:58 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.