Skip to content
New issue

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

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

Already on GitHub? # to your account

Default guestid other-64 isn't working on vsphere_virtual_machine resource #1263

Closed
izecevic opened this issue Nov 17, 2020 · 1 comment · Fixed by #1543
Closed

Default guestid other-64 isn't working on vsphere_virtual_machine resource #1263

izecevic opened this issue Nov 17, 2020 · 1 comment · Fixed by #1543
Labels
bug Type: Bug

Comments

@izecevic
Copy link

Terraform Version

  • Terraform v0.12.24

vSphere Provider Version

  • provider.vsphere v1.24.2

Affected Resource(s)

  • vsphere_virtual_machine

Debug Output

Basically, if I am referring to the following documentation: https://registry.terraform.io/providers/hashicorp/vsphere/latest/docs/resources/virtual_machine

It seems that the guest_id is optional and by default set to other-64
--> guest_id - (Optional) The guest ID for the operating system type. For a full list of possible values, see here. Default: other-64.

However, applying the state (deploying a new vm) fails with the following error code:
vsphere_virtual_machine.vm: Creating... Error: error creating virtual machine: A specified parameter was not correct: configSpec.guestId on main.tf line 36, in resource "vsphere_virtual_machine" "vm": 36: resource "vsphere_virtual_machine" "vm" {

However, the default guest_id (other-64) doesn't exist if we look at VMware's guest documentation available here: https://code.vmware.com/apis/358/doc/vim.vm.GuestOsDescriptor.GuestOsIdentifier.html

The default value I think is/should be: otherGuest64 (based on that list)

--

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@izecevic izecevic added the bug Type: Bug label Nov 17, 2020
appilon pushed a commit that referenced this issue Jan 14, 2022
- Updates the default GOS to `otherGuest64` from `other-64` (invalid).
- Updates `guest_id` and `alternate_guest_name` to correctly mention `otherGuest` and `otherGuest64` - not `other` and `other-64`
- Also updates the descriptions in `virtual_machine_config_structure.go` with more inclusive terminology, cleaner structure, and correct component proper name.

Reference: #1263

Signed-off-by: Ryan Johnson <johnsonryan@vmware.com>
@github-actions
Copy link

I'm going to lock this issue 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 similar to this, 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 Feb 14, 2022
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
bug Type: Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant