-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Comments
As added context for the problem described above, we are following the notes from documentation:
Thank you in advance for the assistance |
This issue has been migrated to hashicorp/packer-plugin-vsphere#213 due to the Packer Plugin split. Please follow the new issue for updates. |
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. |
Community Note
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.
The text was updated successfully, but these errors were encountered: