Can't manage netbox_virtual_machine

[felipeneuwald]

Hey guys, any idea why this is happening?

Terraform Version

$ terraform version
Terraform v0.13.3

• provider registry.terraform.io/e-breuninger/netbox v0.0.3
• provider registry.terraform.io/terraform-provider-openstack/openstack v1.32.0

Affected Resource(s)

• netbox_virtual_machine

Terraform Configuration Files

terraform {
  backend "http" {
  }
  required_providers {
    openstack = {
      source = "terraform-provider-openstack/openstack"
      required_version = ">= 0.13"
    }
    netbox = {
      source = "e-breuninger/netbox"
      required_version = ">= 0.13"
      version = "0.0.3"
    }
  }
}

provider "openstack" {
  user_name   = "***"
  tenant_name = "***"
  password    = "***"
  auth_url    = "***"
  region      = "***"
}

provider "netbox" {
  server_url = "***"
  api_token  = "***"
}

resource "netbox_virtual_machine" "testvm" {
  name         = "my-test-vm"
  comments     = "my-test-comment"
  memory_mb    = 1024
  vcpus        = 4
  disk_size_gb = 512
  cluster_id   = 4
  # tenant_id    = netbox_tenant.testtenant.id
  # platform_id  = netbox_platform.testplatform.id
  # role_id      = netbox_device_role.testdevicerole.id
}

Debug Output

https://gist.github.com/felipeneuwald/6374449273ce2b345f29da03254e405c

Panic Output

Expected Behavior

Apply the changes

Actual Behavior

Error

Steps to Reproduce

1. terraform apply

Important Factoids

References

[fbreckle]

I just released a new version that is compatible with netbox 2.9.8. While I do not think your issue is caused by the wrong netbox version, the new provider version also comes with vastly improved error handling and should now propagate the actual API error correctly instead of giving you err: unknown error (status 400).

If I had to guess in your case, I'd say your error is a Virtual machine with this Cluster, Tenant and Name already exists..

[fbreckle]

Closed due to inactivity and very old provider version.