terraform-provider-vsphere: v1.16 ERROR:ServerFaultCode: NoPermission

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

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 6
Comments: 19 (5 by maintainers)

Most upvoted comments

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. However, it seems that the global read only do not cover the profile-driven storage. With the complementary access “profile-driven storage view”, it work!

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.

arsiesys on Feb 4, 2020

Hello,

Same issue here.

After debug, it’s related the following change: https://github.com/terraform-providers/terraform-provider-vsphere/pull/881/commits/12e2fc95bdfbfccdcad245919ebd09158c266746

Could we know which access/role name is missing to be able to fix it ? :p Thanks!

arsiesys on Feb 4, 2020