Bug 2247345

Hello,

I believe this issue is also related to the current behavior

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

Waldirio

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

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.

*** Bug 2247081 has been marked as a duplicate of this bug. ***

(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..

Chris, can you take a look at it? The number of customers reporting broken V8 is growing every day.

Leos,

I will start to break down this epic and get it refined and start to see what needs to be worked on.

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.

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.