-
Notifications
You must be signed in to change notification settings - Fork 112
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
help plz - error Creating OrgvDC for an already existing Organization #1335
Comments
hello @adambarreiro and many thanks for your reply, Stack trace from the terraform-provider-vcd_v3.10.0 plugin: panic: assignment to entry in nil map goroutine 45 [running]: Error: The terraform-provider-vcd_v3.10.0 plugin crashed! This is always indicative of a bug within the plugin. It would be immensely
|
I think it's the same issue reported here: #1098, it was fixed in Provider v3.11.0. I remember you mentioned you were using VCD 10.3, which v3.11.0 does not support. Any chances of upgrading VCD? |
thanks @adambarreiro for your reply |
hello, im new to Tf and whenever i try creating an OrgvDC for an existing Organization, im getting an error as per below:
"Error: The terraform-provider-vcd_v3.10.0 plugin crashed!
This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed."
below is a snippet of the main.tf containing the lines for this OrgvDC creation where everything looks straight forward:
resource "vcd_org_vdc" "vdc-name" {
name = var.vdc_name
org = var.org_name
allocation_model = var.vdc_alloc_model
provider_vdc_name = var.vdc_pvdc_name
network_quota = 50
compute_capacity {
cpu {
limit = 0
}
memory {
limit = 0
}
}
storage_profile {
name = var.vdc_storage_name
enabled = true
limit = 10240
default = true
}
enabled = true
enable_thin_provisioning = true
enable_fast_provisioning = true
delete_force = true
delete_recursive = true
depends_on = [ vcd_org.org-name ]
}
Any help is much appreciated
Rgds
The text was updated successfully, but these errors were encountered: