Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vsphere vm with two networks and two nics #1328

Closed
tfiedler opened this issue Feb 3, 2021 · 3 comments
Closed

vsphere vm with two networks and two nics #1328

tfiedler opened this issue Feb 3, 2021 · 3 comments
Labels
bug Type: Bug duplicate Status: Duplicate Issue

Comments

@tfiedler
Copy link

tfiedler commented Feb 3, 2021

Terraform Version

vSphere Provider Version

Affected Resource(s)

  • vsphere_virtual_machine

Terraform Configuration Files

data "vsphere_network" "net1" {
  name          = "somenetwork"
  datacenter_id = data.vsphere_datacenter.dc.id
}

data "vsphere_network" "net2" {
  name          = "somothernetwork"
  datacenter_id = data.vsphere_datacenter.dc.id
}

Then in the vsphere_virtual_machine section

resource "vsphere_virtual_machine" "vm" {

 network_interface {
    network_id = data.vsphere_network.net1.id
    adapter_type = "vmxnet3"
  }

  network_interface {
    network_id = data.vsphere_network.net2.id
    adapter_type = "vmxnet3"
  }

And in customization

network_interface {
  ipv4_address = "192.168.102.87"
  ipv4_netmask = 24
  dns_domain = var.dns_domain
  dns_server_list = var.dns_server_list
}

network_interface {
  ipv4_address = "10.3.1.19"
  ipv4_netmask = 24
}

Debug Output

Error: POST https://cloud9.lab.yolo.com/rest/com/vmware/vcenter/ovf/library-item/id:937fe71e-1b83-4e11-8097-b5b8e91cc317?~action=deploy: 500 Server Error

  on main.tf line 70, in resource "vsphere_virtual_machine" "vm":
  70: resource "vsphere_virtual_machine" "vm" {

Panic Output

Expected Behavior

Id have expected that two nics get created with the attributes in the config.

Actual Behavior

Error 500 from server (vcenter)

Steps to Reproduce

Important Factoids

Im not sure if this is important but this is getting deployed from a content library ovf, The ovf this is being pulled rom only has 1 nic, and I suspect thats what Im running into. Im unsure how to resolve it.

References

  • #0000

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@tfiedler tfiedler added the bug Type: Bug label Feb 3, 2021
@tenthirtyam
Copy link
Collaborator

Based on the debug output the source is an OVF from the content library.

POST https://cloud9.lab.yolo.com/rest/com/vmware/vcenter/ovf/library-item/id:937fe71e-1b83-4e11-8097-b5b8e91cc317?~action=deploy: 500 Server Error

Does the originating OVF Template have two NICs? If note, per the VMware vSphere product documentation, which compares the use of VM Templates vs OVF Templates in Content Library:

"During the deployment of an OVF template, only guest OS customization is supported. Hardware customization is not supported."

Reference: The VM Template as a Content Library Item

Duplicate of #1345 and similar to #1441.

Regards,
Ryan

cc @appilon and @iBrandyJackson for review.

@appilon appilon added the waiting-response Status: Waiting on a Response label Jan 17, 2022
@appilon appilon added the duplicate Status: Duplicate Issue label Jan 28, 2022
@appilon
Copy link
Contributor

appilon commented Jan 28, 2022

Closing duplicate, please open a new issue if the issue persists.

@appilon appilon closed this as completed Jan 28, 2022
@github-actions github-actions bot removed the waiting-response Status: Waiting on a Response label Jan 28, 2022
@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Type: Bug duplicate Status: Duplicate Issue
Projects
None yet
Development

No branches or pull requests

3 participants