Bug #36023: VMWare Guest OS list is outdated - Foreman

Actions

Copy link

Bug #36023

closed

VMWare Guest OS list is outdated

Added by Alexander Olofsson almost 2 years ago. Updated 6 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Compute resources - VMware

Target version:

3.11.0

Difficulty:

Triaged:

Yes

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/10092

Fixed in Releases:

3.11.0

Found in Releases:

3.2.2, 3.5.0

Red Hat JIRA:

Description

We've started deploying Windows Server 2022 VMs on our VMWare cluster now, an OS that is not included in the Foreman Guest OS list - even in the latest commits of the develop branch.
When such a host is cloned, things break in all manner of horrible and hilarious ways - it ends up defaulting to MS-DOS and munging device configuration based on that.

An updated list turns out to be difficult to come by without a working VMWare setup, but we were able to use the steps in https://communities.vmware.com/t5/VMware-PowerCLI-Discussions/How-to-get-all-VirtualMachineGuestOsIdentifier-over-PowerCLI/m-p/1397700/highlight/true#M45704 to generate a list that's up-to-date with vSphere 7.0U3
The resulting (CSV-encoded) list has been attached for now, hopefully I'll have time to write up a proper patch as well once time allows.

Files

vmware_os.csv

6.82 KB

Current OS list as of vSphere 7.0U3i (build 20845200)

Alexander Olofsson, 01/31/2023 02:22 PM

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Ewoud Kohl van Wijngaarden almost 2 years ago

I think the version is relevant. We just updated to fog-vsphere 3.6 which switched from rbvmomi to rbvmomi2, but that's only in nightly. You do mention develop, but can you also verify rbvmomi2 is used? I believe that uses the vmodl.db file to provide the definitions.

Actions

Copy link

Updated by Alexander Olofsson almost 2 years ago

The mapping list for OS versions that this updated list relates to is still hardcoded in Foreman code - a.k.a. https://github.com/theforeman/foreman/blob/develop/app/models/compute_resources/foreman/model/vmware.rb#L232-L398
Not sure if it's possible to generate it, since the upstream documentation fails to do so for any vSphere newer than 6.7, but getting the descriptions off of a running cluster proved doable.

It's likely that an updated vmodl.db will help as well in regards to the cloning issues, but I've not been able to actually test that yet. I might be able to look at further tests on our local systems some time next month, but until then the updated description mapping remains attached here.

Actions

Copy link