-
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 label inconsistency with VDS in vCenter folder #8584
Comments
same for me here |
I have the same problem. Thanks! |
Hi, is there a solution for the issue? |
+1
|
Hi, My network label is "v686 10.10.0.0/16" So, it contains space and forward slash. While executing i am getting same error : Network not found. Any idea how to get rid of this ? Thanks, |
Hello
What version of terraform you running ?
Regards
James
…On Fri, Sep 15, 2017 at 11:41 AM, sidhurana ***@***.***> wrote:
Hi,
My network label is "v686 10.10.0.0/16" So, it contains space and forward
slash. While executing i am getting same error : Network not found.
Any idea how to get rid of this ?
Thanks,
Sudhir
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8584 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADqtORVpP2L47qWy3xBOnW-u6RMSvf7Pks5silRlgaJpZM4JyCTD>
.
|
Hi James, Terraform version: 0.9.2 |
Just tried with latest version.i.e. 0.10.5. Got same results. |
yeah was thinking in a later version might fix this
…On Fri, Sep 15, 2017 at 12:49 PM, sidhurana ***@***.***> wrote:
Just tried with latest version. Got same results.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#8584 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADqtOZVCxYYQLngnV5pRNZdx0LWUpvlNks5simRYgaJpZM4JyCTD>
.
|
I've also run into this same issue on the latest version 0.10.6 @lvlie thanks for the workaround! There is also a bug report in the provider repo: hashicorp/terraform-provider-vsphere#11 |
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. |
Running into an issue with networking in the vsphere provider:
Terraform cannot locate the network interface label when the virtual distributed switch (vds) is located in a folder, unless the folder is added to the label path (e.g., 'folder/label'). Once the VM is deployed, if another Terraform plan/apply is run against the resource it will identify the network interface label as not containing the folder, thus requiring the resource to be recreated or config changed.
Terraform Version
Terraform v0.7.2
vSphere Version
vSphere 6.0
Affected Resource(s)
Error Example
When the config includes just the label it cannot find the label:
When the label includes folder, it deploys fine but it does not match the label returned when planning/applying:
The text was updated successfully, but these errors were encountered: