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

Packer cannot find network in vCenter #11963

Closed
eperts opened this issue Aug 30, 2022 · 3 comments
Closed

Packer cannot find network in vCenter #11963

eperts opened this issue Aug 30, 2022 · 3 comments

Comments

@eperts
Copy link

eperts commented Aug 30, 2022

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

I'm trying to run a Packer build to get a windows 10 template for Horizon VDI. My build runs fine in our lab environment, but in our production environment, it cannot find the correct network. There are several networks with the same name so I am specifying the entire path down to the correct network. Using the same structure that worked without issues in our lab environment, it does not work in the production environment.

The error that comes back is: Invalid configuration for device '0'.

I cannot use a different network for the production vCenter.

When I cut it down to just the network name, it comes back with an error: path '' resolves to multiples provide a host to match or full network path.

The path I'm using is, essentially: //network//

Again, this works in our test vCenter, but not production. If anyone has run into this issue before, I'd appreciate any advice.

@eperts eperts added the bug label Aug 30, 2022
@github-actions github-actions bot removed the bug label Aug 30, 2022
@jpinto13
Copy link

As added context for the problem described above, we are following the notes from documentation:
"[network] (string) - Set the network in which the VM will be connected to. If no network is specified, host must be specified to allow Packer to look for the available network. If the network is inside a network folder in vCenter, you need to provide the full path to the network."
As stated the path we use goes: "/DC/network/dvswitch/distributedportgroup", while using this string in our code packer fails with the error stated before. We need to identify how to provide the string for a Distributed Port Group that the same name is use on a different dvswitch inside the same Datacenter just like the below:

  • /DC1/network/dvswitch1/distributedportgroup1
  • /DC1/network/dvswitch2/distributedportgroup1
  • /DC1/network/dvswitch3/distributedportgroup1

Thank you in advance for the assistance

@github-actions
Copy link

This issue has been migrated to hashicorp/packer-plugin-vsphere#213 due to the Packer Plugin split.

Please follow the new issue for updates.

@github-actions
Copy link

github-actions bot commented Oct 1, 2022

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 Oct 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants