Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 1939 #1995

Merged
merged 3 commits into from
Aug 17, 2023
Merged

Issue 1939 #1995

merged 3 commits into from
Aug 17, 2023

Conversation

nklinkachevAtVMware
Copy link
Contributor

@nklinkachevAtVMware nklinkachevAtVMware commented Aug 17, 2023

Description

Bugfix for [issue 1939] (#1939)
Cloning and configuring VMs with newer guest operating systems (Windows 2022 in this case) was failing in some cases due to the backend using the ESXi default hardware version instead of the template or VM hardware version being cloned from or configured. This was causing the guest OS to not be recognised as supported.
Changed the backend pass the hardware version when retrieving the OS family.

Acceptance tests

  • Have you added an acceptance test for the functionality being added?
  • Have you run the acceptance tests on this branch?

Output from acceptance testing:

no regressions

Release Note

Release note for CHANGELOG:

`r/virtual_machine`: Fix "Error: cannot find OS family for guest ID ... " when cloning and/or configuring a VM/Template ([#1939](https://github.com/hashicorp/terraform-provider-vsphere/issues/1939))

References

Closes #1939

Supported guest OS are dependent on the VM hardware version. Changed querying the OS Family when deploying a VM from template to read the template hardware version instead of using the server default version.
The code now correctly reads hardware version from the template and the terraform spec and passes along the higher of the two values to the environment browser.
This allows configuration of vm deployments from templates with OSes newer than what the default hardware compatibility version of the ESXi server allows.
@nklinkachevAtVMware nklinkachevAtVMware requested a review from a team as a code owner August 17, 2023 19:27
@hashicorp-cla
Copy link

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

@github-actions github-actions bot added provider Type: Provider size/s Relative Sizing: Small labels Aug 17, 2023
@appilon appilon merged commit 820788a into main Aug 17, 2023
@appilon appilon deleted the issue-1939 branch August 17, 2023 19:53
@appilon appilon mentioned this pull request Sep 1, 2023
2 tasks
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
provider Type: Provider size/s Relative Sizing: Small
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unable to create new Windows Server 2022 VM via Terraform in VMware Cloud (VMC) from template and customize
3 participants