-
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
vcd 3.4.0 vcd_vapp_vm Error: error finding catalog name: [ENF] entity not found #744
Comments
@neticenet , Now I need more information on what kind of catalog you have. Is it shared? Any more specific on the catalog and also a log bundle would most probably be required to understand. |
@Didainius, My catalog "OKD" catalog type Shared. |
catalog_name = "okd" Catalog name is case sensitive.
|
@Filsbo |
@neticenet, |
@Didainius |
The lookup did change in 3.3.0 since it did not work the same way after API bump. What type of image do you use? is it ova? |
@Didainius |
Hi @neticenet |
This looks to be stuck. Closing it. @neticenet , can you share additional details if the issue persists with latest provider version. Thanks |
Hello!
After updating the provider to version 3.4.0, I cannot create vcd_vapp_vm. I get:
Error: error finding catalog okd: [ENF] entity not found
Although on version 3.1.0 it works fine.
Terraform Version
Terraform v1.0.11
on darwin_amd64
Affected Resource(s)
vcd_vapp_vm
Terraform Configuration Files
resource "vcd_vapp_vm" "vms" {
name = "test-vm"
catalog_name = "okd"
template_name = "okd-templ"
memory = 8192
cpus = 2
storage_profile = "SSD"
}
data "vcd_org" "my-org" {
name = var.VCD_ORG
}
data "vcd_org_vdc" "my-org-vdc" {
org = var.VCD_ORG
name = var.VCD_VDC
}
Panic Output
│ Error: error finding catalog okd: [ENF] entity not found
│
│ with vcd_vapp_vm.vms,
│ on main.tf line 58, in resource "vcd_vapp_vm" "vms":
│ 58: resource "vcd_vapp_vm" "vms" {
│
Additional Information
The code runs correctly on version 3.1.0
The code ends with a bug on versions 3.3.1, 3.4.0
References
The text was updated successfully, but these errors were encountered: