-
Notifications
You must be signed in to change notification settings - Fork 447
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
v1.16 ERROR:ServerFaultCode: NoPermission #966
Comments
Same here,
Thanks |
Seeing the same issue here as well... |
We are experiencing the same issue with v1.16 - Please see our error in context of DEBUG log 2020-02-04T15:15:37.988Z [DEBUG] plugin.terraform-provider-vsphere_v1.16.0_x4: 2020/02/04 15:15:37 [DEBUG] VM “/“path/to/our/template/ISO found for UUID "4201b507-7907-3b1a-55d3-cdef9f4264cd" |
Hello, Same issue here. After debug, it's related the following change: Could we know which access/role name is missing to be able to fix it ? :p |
Thank you for filing this issue - we're investigating the problem |
I'm working on tracking down the potential causes of this issue. There are a few data points I could use that would help make sure I cover all the cases.
Thanks, and I'll provide updates shortly. |
Hello @bill-rich, We are running in Vcenter 6.5. The user running terraform had some specific RW access on ressources pools/Datastore and was running fine in 1.15. Also, the user had a global read only access on the vcenter. I guess it could be good to document (or catch the error and print a detailed output) it as we will not be the only ones to get impacted :p. |
The same we have: err: disk.0: validation failed (ServerFaultCode: NoPermission) |
Also just started getting this error:Error: Error running plan: 2 errors occurred:
|
Previously:We were experiencing the above (v1.16 ERROR:ServerFaultCode: NoPermission #966) error We were running Terraform v0.11.11 with v1.16 vsphere provider against vCenter 6.7 / ESXi 6.5 We got the following error: err: disk.0: validation failed (ServerFaultCode: NoPermission) Now:I tried to work-around this problem I still get the following error running terraform plan
I would like to have a working approach for vCenter 6.7 if possible It would also help to know how to select a specific vSphere provider version say v1.15.0 I tried the following stanza which seemed to agree with the provider documentation at provider "vsphere" { However, my terraform run continues to use 1.16.0 [terraform@nohost]$ /var/tmp/terraform init
I looked for a state file to determine whether I needed to purge that but there isn't one in the pwd after the terraform plan nor is there one anywhere else on the host |
You need to specify the version string correctly:
The key being the |
That worked - thanks for your help Josh |
Thanks for testing that @arsiesys! For everyone still experiencing this issue, it looks like is is due to new permissions being required for the addition of SPBM support in v1.16.0. Please check that the user Terraform is running as has "Profile-driven storage" permissions at the vCenter. I will get the changelog updated with notes about the additional permissions. |
Still fails with v0.12.20 and v1.16.1 $ egrep -i 'terraform|1.16' terraform.log | head Error: The virtual machine may still exist in Terraform state. If it does, the If the virtual machine does not exist in state, manually delete it to try again. on config.tf line 35, in resource "vsphere_virtual_machine" "vm": |
@glenfiddich have you ensured this - |
Upgrade to 1.16.1 and provide the mentioned permissions "Profile-driven storage" fixed it for us. |
Plugin version 1.16.2. It's seems that it is necessary to set "Profile-driven storage" policy at the root group of vcenter server. Fixed for us. |
Closing this issue - please create a new issue if this recurs in current or future versions of the provider. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Hi,
We ran into an issue this morning with not being able to create any new nodes on our vsphere.
Not a lot of usefull output with only error showing when applying a plan being
Error: ServerFaultCode: NoPermission
Setting the output to trace revealed a little more, getting the following output during the plan stage.
4261 Error: ServerFaultCode: NoPermission
4262 2020-02-04T12:45:39.115Z [DEBUG] plugin: plugin process exited: path=/build/terraform/terraform-windows-vm/projects/.terraform/plugins/linux_amd64/terraform-provider-vsphere_v1.16.0_x4 pid=202
4263 Error: ServerFaultCode: NoPermission
4264 2020-02-04T12:45:39.115Z [DEBUG] plugin: plugin exited
4265 Error: ServerFaultCode: NoPermission
4266 Error: ServerFaultCode: NoPermission
4267 Error: ServerFaultCode: NoPermission
4268 Error: ServerFaultCode: NoPermission
4269 Error: ServerFaultCode: NoPermission
4270 Error: ServerFaultCode: NoPermission
4271 Error: ServerFaultCode: NoPermission
4272 Error: ServerFaultCode: NoPermission
4273 2020-02-04T12:45:39.116Z [DEBUG] plugin: plugin process exited: path=/builds/terraform/terraform-windows-vm/projects/.terraform/plugins/linux_amd64/terraform-provider-vsphere_v1.16.0_x4 pid=189
4274 2020-02-04T12:45:39.116Z [DEBUG] plugin: plugin exited
4275 Error: ServerFaultCode: NoPermission
4276 ERROR: Job failed: exit code 1
Terraform Version: 0.12.18
vSphere Provider Version : 1.16.0
Our account according to IT has full admin privalges on vsphere, reverting back to vsphere plugin version 1.15.0 and hard locking to that version fixed it for us.
Let me know if you need more information and I try and help
Thanks,
Tristan
The text was updated successfully, but these errors were encountered: