Crash Report when applying a vsphere machine about terraform-provider-vsphere HOT 6 CLOSED

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.

from terraform-provider-vsphere.

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

from terraform-provider-vsphere.

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.

from terraform-provider-vsphere.

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

from terraform-provider-vsphere.

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

from terraform-provider-vsphere.

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!

from terraform-provider-vsphere.