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 2247345 - [RFE] ability to provision on vCenter 8.x
Summary: [RFE] ability to provision on vCenter 8.x
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.13.5
Hardware: All
OS: All
high
high with 1 vote
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks: 2255264 2272649
TreeView+ depends on / blocked
 
Reported: 2023-11-01 00:16 UTC by Waldirio M Pinheiro
Modified: 2024-06-16 11:45 UTC (History)
20 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-21075 0 None Migrated None 2024-06-06 16:31:34 UTC
Red Hat Knowledge Base (Solution) 7041596 0 None None None 2023-11-01 00:17:11 UTC

Internal Links: 2249488

Description Waldirio M Pinheiro 2023-11-01 00:16:14 UTC 
Description of problem:
Be sure that satellite 6.13+ is able to provision on vCenter 8.x

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

How reproducible:
In the customer environment

Steps to Reproduce:
1. Prepare satellite
2. Create the compute resource
3. Use the boot disk based method

Actual results:
Error when provisioning

Expected results:
Provision with no issues

Additional info:
Comment 1 Waldirio M Pinheiro 2023-11-01 00:18:24 UTC 
Hello,

I believe this issue is also related to the current behavior

https://bugzilla.redhat.com/show_bug.cgi?id=2247081

Waldirio
Comment 2 Waldirio M Pinheiro 2023-11-01 00:21:15 UTC 
Hello,

Just to keep on track, Satellite 6.13 supports vCenter version 6.x and 7.x. At this moment, we have no support for vCenter 8.x, which is the main idea of this bugzilla.

Here is the doc.

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/provisioning_hosts/index#Creating_a_VMware_User_vmware-provisioning

Best
Waldirio
Comment 3 Sayan Das 2023-11-01 07:49:56 UTC 
I would like to suggest a modification in "Steps to reproduce" assuming we are not considering it as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2247081 but rather this BZ would be used to test and confirm that vSphere 8 is compatible 

Steps to Reproduce:
1. Prepare satellite 6.13 or 6.14
2. Create the compute resource for VMware vSphere 8
3. Test the following system deployments using that compute resource:

    * Normal PXE
    * Auto-attach bootdisk 
    * Image based ( USerdata\Cloud-init )


If with bootdisk we have this bug 2247081, then It's possible that something similar would also happen with Image-based ( where cloning is involved ), and hence thorough testing should be done.
Comment 4 Ron Lavi 2023-11-06 13:40:04 UTC 
*** Bug 2247081 has been marked as a duplicate of this bug. ***
Comment 6 rmassey 2023-11-07 16:01:03 UTC 
(In reply to Waldirio M Pinheiro from comment #2)
> Hello,
> 
> Just to keep on track, Satellite 6.13 supports vCenter version 6.x and 7.x.
> At this moment, we have no support for vCenter 8.x, which is the main idea
> of this bugzilla.
> 
> Here is the doc.
> 
> https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-
> single/provisioning_hosts/index#Creating_a_VMware_User_vmware-provisioning
> 
> Best
> Waldirio

Just for a little more context, the doc you provided doesn't say vCenter 8 is NOT supported.  It just gives you advice on versions 6.x and 7.x.  vCenter versions 6.x reached EOL in October 2022.  The absolute end of technical support is November 15, 2023.  I can confirm that RedHat Satellite 6.13 works with vCenter 8.0.  It is not until vCenter version 8.02 that this problem was introduced.

With all products, there are some problems that are resolved with more current versions of the software.  vCenter is no different.  At this point, the lack of official support for vCenter 8 in RedHat Satellite 8.x is very problematic as it forces you to stay on a problematic versions of vCenter to maintain compatibility with Satellite..
Comment 7 Leos Stejskal 2023-11-21 08:51:02 UTC 
Chris, can you take a look at it? The number of customers reporting broken V8 is growing every day.
Comment 9 Chris Roberts 2023-11-28 16:27:13 UTC 
Leos,

I will start to break down this epic and get it refined and start to see what needs to be worked on.
Comment 11 Marek Hulan 2024-04-16 08:33:39 UTC 
Chris, any updates? It seems the bootdisk fix is in upstream already. Were there some other issues that need to be fixed? I guess so, since you've reverted this BZ from POST back to NEW, but there was no context. FTR, the bootdisk issue is fixed in foreman_bootdisk-21.2.2 and fog-vsphere 3.6.4.
Comment 15 Eric Helms 2024-06-06 16:31:36 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.