Crash Report when applying a vsphere machine

[hashibot]

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

---

I was running terraform apply and had a crash.

Output from consule before the crash

vsphere_virtual_machine.ldap: Creating...
  cluster:                         "" => "main"
  datacenter:                      "" => "home"
  disk.#:                          "" => "2"
  disk.0.datastore:                "" => "ssd1"
  disk.0.template:                 "" => "templates/centos71-v0.5.18"
  disk.1.datastore:                "" => "ssd1"
  disk.1.size:                     "" => "10"
  domain:                          "" => "int.ehdev.io"
  memory:                          "" => "768"
  name:                            "" => "infrastructure-ldap-1"
  network_interface.#:             "" => "2"
  network_interface.0.ip_address:  "" => "<computed>"
  network_interface.0.label:       "" => "Infa VM"
  network_interface.0.subnet_mask: "" => "<computed>"
  network_interface.1.ip_address:  "" => "<computed>"
  network_interface.1.label:       "" => "Infa VM"
  network_interface.1.subnet_mask: "" => "<computed>"
  time_zone:                       "" => "America/Los_Angeles"
  vcpu:                            "" => "1"
Error applying plan:

1 error(s) occurred:

* vsphere_virtual_machine.ldap: 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.
panic: interface conversion: interface is nil, not string

Terraform Version

> terraform --version
Terraform v0.6.8

Crash Log

crash.txt

[hashibot]

This comment was originally opened by @ethankhall as hashicorp/terraform#4302 (comment). It was migrated here as part of the provider split. The original comment is below.

---

The issue happens when you have a network interface that doesn't have an IP address. Making the second NIC get an IP lets apply continue. This can happen if you use systemd-networkd and you don't have the catchall dhcp setup and only one nic get an IP.

[hashibot]

This comment was originally opened by @phinze as hashicorp/terraform#4302 (comment). It was migrated here as part of the provider split. The original comment is below.

---

Relevant snippet from the crash log:

2015/12/13 18:34:37 [DEBUG] terraform-provider-vsphere: panic: interface conversion: interface is nil, not string
2015/12/13 18:34:37 [DEBUG] terraform-provider-vsphere: 
2015/12/13 18:34:37 [DEBUG] terraform-provider-vsphere: goroutine 82 [running]:
2015/12/13 18:34:37 [DEBUG] terraform-provider-vsphere: github.com/hashicorp/terraform/builtin/providers/vsphere.resourceVSphereVirtualMachineRead(0xc8202e7980, 0xefc100, 0xc8203d7eb0, 0x0, 0x0)
2015/12/13 18:34:37 [DEBUG] terraform-provider-vsphere:     /private/tmp/terraform20151202-21396-jm3im7/terraform-0.6.8/src/github.com/hashicorp/terraform/builtin/providers/vsphere/resource_vsphere_virtual_machine.go:427 +0x2121
2015/12/13 18:34:37 [DEBUG] terraform-provider-vsphere: github.com/hashicorp/terraform/builtin/providers/vsphere.resourceVSphereVirtualMachineCreate(0xc8202e7980, 0xefc100, 0xc8203d7eb0, 0x0, 0x0)
2015/12/13 18:34:37 [DEBUG] terraform-provider-vsphere:     /private/tmp/terraform20151202-21396-jm3im7/terraform-0.6.8/src/github.com/hashicorp/terraform/builtin/providers/vsphere/resource_vsphere_virtual_machine.go:344 +0x1af3

[hashibot]

This comment was originally opened by @chrislovecnm as hashicorp/terraform#4302 (comment). It was migrated here as part of the provider split. The original comment is below.

---

We are currently rewriting that block of code, because of another issue.hashicorp/terraform#4112 - this is not a duplicate issue, but is in the exact same code blocks.

@tkak something else to consider. I noticed that possible nil previously, and forgot to file an issue.

[hashibot]

This comment was originally opened by @chrislovecnm as hashicorp/terraform#4302 (comment). It was migrated here as part of the provider split. The original comment is below.

---

Will push this in a large PR that I am working on

[hashibot]

This comment was originally opened by @chrislovecnm as hashicorp/terraform#4302 (comment). It was migrated here as part of the provider split. The original comment is below.

---

Fixed in hashicorp/terraform#7031 - when merged

[vancluever]

This issue is dated, and with the 1.x release, the referenced bug is more than likely no longer relevant. If anyone is still getting a crash related to this issue, please open a new issue with the pertinent details!