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: do not add new network adapters by default #3559

Closed
mkuzmin opened this issue Oct 20, 2015 · 1 comment · Fixed by #3652
Closed

vSphere: do not add new network adapters by default #3559

mkuzmin opened this issue Oct 20, 2015 · 1 comment · Fixed by #3652

Comments

@mkuzmin
Copy link
Contributor

mkuzmin commented Oct 20, 2015

An the moment a new network adapter is added every time a virtual machine is created.
A quote from https://github.com/rakutentech/terraform-provider-vsphere/blob/master/README.md:

please don't include network adapters in VM template. When deploying a new virtual machine, this provider adds new network adapters to the new virtual machine.

This requirement is fine, if a machine is created from scratch, and then loaded from PXE. But that's not the main use case.
More often machines are cloned from templates, and here such requirement makes the procedure extremely complicated. To make my templates compatible to Terraform, I have to remove network adapters explicitly. But what if later I need to update such a template? I have to add a network adapter back, load a machine, make required changes, and then delete the adapter once again. That just doesn't work.

If Terraform clones a virtual machine from a template, then network_interface parameter must be optional. By default it should inherit configuration from a template, and do not create additional network adapters.

@ghost
Copy link

ghost commented Apr 30, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants