Set SCSI controller type to unknown when nil

[bill-rich]

There can be fewer controllers than expected when deploying from content library or ovf. Setting the controller type to unknown will block further use without crashing.

[lmayorga1980]

I don't think this is fixing the issue

provider "vsphere" {
  user                 = var.vsphere_user
  password             = var.vsphere_password
  vsphere_server       = var.vsphere_server
  allow_unverified_ssl = true
}

data "vsphere_datacenter" "dc" {
  name = "LABDC"
}

data "vsphere_datastore" "datastore" {
  name          = "MYLAB01"
  datacenter_id = data.vsphere_datacenter.dc.id
}

data "vsphere_resource_pool" "pool" {
  name          = "CLUSTERLAB/Resources"
  datacenter_id = data.vsphere_datacenter.dc.id
}

data "vsphere_network" "network" {
  name          = "VM-123"
  datacenter_id = data.vsphere_datacenter.dc.id
}

data "vsphere_virtual_machine" "template" {
  name          = "vmware-vm-centos82"
  datacenter_id = data.vsphere_datacenter.dc.id
}

I am having an issue with either specifying a VSphere VM Template(Offline) or a VSphere VM(Offline) and I am not trying to create a VM yet.

It crashes with the snippet

data "vsphere_virtual_machine" "template" {
  name          = "vmware-vm-centos82"
  datacenter_id = data.vsphere_datacenter.dc.id
}

[lmayorga1980]

Fixed on 1.24

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!