-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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 network interfaces #3560
Comments
As an issue reporter, you can close it by yourself. |
@mkuzmin yep, thanks. |
eloycoto
added a commit
to foehn/terraform
that referenced
this issue
Oct 27, 2015
before added new one. Fixes hashicorp#3559 and hashicorp#3560
dpetzold
pushed a commit
to clearcare/terraform
that referenced
this issue
Nov 12, 2015
before added new one. Fixes hashicorp#3559 and hashicorp#3560
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
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.
Hi,
Using the following config, we have the following issue:
The template (x_template) has one network address, when terraform clone the template, terraform added a new network interface, so the vsphere crash with NicSeetingMismatch.
If my template doesn't have any network interface works ok. Is this the correct process? Or the system need to update the label of the interfaces?
If the template has one interface, the system added a new one.
Our POV is the system need to update the interfaces or create a new ones, but not sure that we are correct.
Regards.
The text was updated successfully, but these errors were encountered: