Plugin did not respond : Stack trace from the terraform-provider-vsphere_v2.8.2_x5.exe plugin

[Josegc1989]

Community Guidelines

• I have read and agree to the HashiCorp Community Guidelines .
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Terraform

2.31

Terraform Provider

2.8.2

VMware vSphere

7

Description

When I run terraform plan o apply the terminal give me the next error:

Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: Plugin did not respond
│
│ with vsphere_virtual_machine.vm,
│ on VM desde Plantilla.tf line 36, in resource "vsphere_virtual_machine" "vm":
│ 36: resource "vsphere_virtual_machine" "vm" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ReadResource call. The plugin logs may contain more details.
╵

Stack trace from the terraform-provider-vsphere_v2.8.2_x5.exe plugin:

panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x8 pc=0x1244bda]

Affected Resources or Data Sources

vm

Terraform Configuration

x

Debug Output

Planning failed. Terraform encountered an error while generating this plan.

Panic Output

No response

Expected Behavior

x

Actual Behavior

x

Steps to Reproduce

x

Environment Details

No response

Screenshots

No response

References

No response

[github-actions]

Hello, Josegc1989! 🖐

Thank you for submitting an issue for this provider. The issue will now enter into the issue lifecycle.

If you want to contribute to this project, please review the contributing guidelines and information on submitting pull requests.

[Josegc1989]

I resolved the problem deleting the archive "terraform.lock.hcl"

[spacegospod]

Hey @Josegc1989 glad to see you have a workaround.
Can you reproduce the problem again with debug logging enabled or at least share your configuration?
There's not enough data to track down the cause of the panic

[spacegospod]

Reporter has indicated that they have resolved the problem, closing the PR

[github-actions]

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.