-
Notifications
You must be signed in to change notification settings - Fork 449
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
Error: cannot find datacenter from path "": NoPermission #854
Comments
Bump |
EDIT-2: For better testing scenario: Hierarchical Inheritance of Permissions below:
|
This issue has been open 180 days with no activity. If this issue is reproducible with the latest version of the provider and with Terraform 0.12, please comment. Otherwise this issue will be closed in 30 days. |
This issue is related to #803 |
It may also be that the permissions are not applied at the vCenter level. They must be applied at the root in order to list datacenters using the vSphere API. |
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 there,
recently we've hardened our VMware vSphere environment and restrict access to parts of the system using roles. Administration of objects via vSphere UI or VMware Workstation Pro works without problem. Unfortunately Terraform has problems with some restrictions.
Terraform Version
vSphere Provider Version
Affected Resource(s)
Please list the resources as a list, for example:
vsphere_folder
Terraform Configuration Files
Debug Output
Panic Output
There is no panic or
crash.log
.Expected Behavior
Create folder.
Actual Behavior
The folder is created, unfortunately I get error message.
Error: cannot find datacenter from path "/BM-LAB": NoPermission
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform plan
terraform apply
Important Factoids
It seems problem comes from https://github.com/terraform-providers/terraform-provider-vsphere/blob/534931a5deb3be12c7217b6794781299fdce28cb/vsphere/resource_vsphere_folder.go#L127 where function
resourceVSphereFolderCreate
returnresourceVSphereFolderRead
, but I don't know why. Comments are missing.Needless to say user connecting to the vSphere has no privileges to view
VC Server
object.EDIT: It's interesting that folder creation in vSphere Web UI works without any problem. Moreover I tested folder creation via govc and it works as well.
The text was updated successfully, but these errors were encountered: