Skip to content
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

vsphere provider fails to create multiple nested folders #38

Closed
hashibot opened this issue Jun 13, 2017 · 1 comment
Closed

vsphere provider fails to create multiple nested folders #38

hashibot opened this issue Jun 13, 2017 · 1 comment
Labels
bug Type: Bug

Comments

@hashibot
Copy link

This issue was originally opened by @jasonk as hashicorp/terraform#8106. It was migrated here as part of the provider split. The original body of the issue is below.


Terraform Version

Terraform v0.7.0

Affected Resource(s)

  • vsphere_folder

Terraform Configuration Files

resource "vsphere_folder" "ci-dev" {
  path = "DevOps/CI/Development"
  datacenter = "Datacenter"
} 

resource "vsphere_folder" "ci-prod" {
  path = "DevOps/CI/Production"
  datacenter = "Datacenter"
} 

resource "vsphere_folder" "ci-test" {
  path = "DevOps/CI/Test" 
  datacenter = "Datacenter"
} 

Expected Behavior

Prior to applying this configuration, the DevOps folder already existed, and I expected that terraform would create the CI folder and then the three subfolders.

Actual Behavior

The CI folder was created, and the Test folder was created underneath it, but errors were thrown for the other two, because apparently terraform tried to create the parent folder three times:

2 error(s) occurred:

* vsphere_folder.ci-prod: Failed to create folder at DevOps/CI; ServerFaultCode: The name 'CI' already exists.
* vsphere_folder.ci-dev: Failed to create folder at DevOps/CI; ServerFaultCode: The name 'CI' already exists.

Steps to Reproduce

  1. terraform apply

Important Factoids

Provisioning against vSphere 5.5, but otherwise a pretty standard setup.

@vancluever
Copy link
Contributor

Creation of subfolders should work so long as you specify multiple resources as documented here.

@ghost ghost locked and limited conversation to collaborators Apr 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Type: Bug
Projects
None yet
Development

No branches or pull requests

2 participants