terraform-provider-vcd: Terraform 0.10.0 crashes when building a new server

This issue was originally opened by @ericlake as hashicorp/terraform#15750. It was migrated here as a result of the provider split. The original body of the issue is below.

---

When trying to create a new server using the vcd provider terraform produces a crash.log file as well as a message stating an EOF error occurred.

Error applying plan:

1 error(s) occurred:

* vcd_vapp.test: 1 error(s) occurred:

* vcd_vapp.test: unexpected EOF

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

Terraform Version

terraform-0.10.0 version
Terraform v0.10.0

Affected Resource(s)

Please list the resources as a list, for example:

• vcd_vapp

I am not sure if this affects more than just this one provider. However this is a new error since 0.9.11 worked. If I rollback to using 0.9.11 and recreate the statefile then this works with everything but the ovf section.

Terraform Configuration Files

global.tf

variable "vcd_user" {}
variable "vcd_pass" {}

provider "vcd" {                                                                                                                                                                
  version              = "0.1.2"
  user                 = "${var.vcd_user}"
  password             = "${var.vcd_pass}"
  org                  = "TEST"
  url                  = "https://director.example.net/api"
  vdc                  = "TEST-VDC"
  maxRetryTimeout      = "1200"
  allow_unverified_ssl = true
}

test.tf

resource "vcd_vapp" "test" {
    count         = "1"
    name          = "test-server"
    catalog_name  = "Zodiac Images"
    template_name = "zodiac-pci-centos-7"
    ip            = "allocated"
    network_name  = "ExNet-RSI-ARTIFACTORY-STAGE"

    metadata {
        role    = "test"
        env     = "test"                                                                                                                                                        
        version = "v1"
    }

    ovf {
        hostname = "test-server"
    }

}

Debug Output

Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.

https://gist.github.com/ericlake/98b31c0e063ee9915798cf1c2ae09662

Panic Output

If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log.

https://gist.github.com/ericlake/d6b63d1daada2d1f2c5246c22083ccb0

Expected Behavior

What should have happened?

The expected behavior is that a new serer would have been created in vmware with the name of test-server.

Actual Behavior

What actually happened?

Instead of getting a new server a terraform had a crash and exited.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. Create a global.tf and a test.tf with the needed variables for a new vapp.
2. With terraform 0.10.0 perform a terraform init
3. Run terraform plan. In my case this exited cleanly.
4. Run terraform apply and the crash happens.

Important Factoids

Are there anything atypical about your accounts that we should know? For example: Running in EC2 Classic? Custom version of OpenStack? Tight ACLs?

None that I can think of.

References

None that I can think of.