You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a resource pool Terraform reports the error
Error: -04T12:18:56.061Z [ERROR] vertex "vsphere_resource_pool.env_rp" error: ServerFaultCode: A specified parameter was not correct: ResourceConfigSpec
Howdy 🖐 adeturner ! Thank you for your interest in this project. We value your feedback and will respond soon.
If you want to contribute to this project, please make yourself familiar with the CONTRIBUTIONguidelines.
adeturner
changed the title
func (p ResourcePool) Create -> ServerFaultCode: A specified parameter was not correct: ResourceConfigSpec
ResourcePool create: ServerFaultCode: A specified parameter was not correct: ResourceConfigSpec
Jan 4, 2024
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Mark as fresh by adding the comment /remove-lifecycle stale.
Describe the bug
I raised an issue against the terraform vsphere provider that appears to me to be a govmoni/vsphere compatibility problem and I'm looking for advice on how to debug.
When creating a resource pool Terraform reports the error
Error: -04T12:18:56.061Z [ERROR] vertex "vsphere_resource_pool.env_rp" error: ServerFaultCode: A specified parameter was not correct: ResourceConfigSpec
This is thrown by govmomi responseUnmarshaler after a call to "func (p ResourcePool) Create"
This gist shows the debug output
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Resource pool is created
Affected version
Provider.terraform-provider-vsphere_v2.6.1_x5
github.com/vmware/govmomi v0.32.0
vSphere Client version 7.0.3.01400
Version: 7.0.3 Build: 21784236
Azure Vmware Solution (if that is useful)
Screenshots/Debug Output
If applicable, add screenshots or debug output to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: