You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Packer v1.7.8, to create a ubuntu 20.04 template on a vcenter server, to be managed by a Saltstack Master!
After, creating the template and spinning up the VM with a Map for Salt, the problem is that there's multiple NICs configured (one from template, and one from Salt-cloud)
The feature request is to be able, after the VM is created to modify the hardware, in this case the specified or all NICs
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 "me too" comments, 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.
The text was updated successfully, but these errors were encountered:
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.
Description
Using Packer v1.7.8, to create a ubuntu 20.04 template on a vcenter server, to be managed by a Saltstack Master!
After, creating the template and spinning up the VM with a Map for Salt, the problem is that there's multiple NICs configured (one from template, and one from Salt-cloud)
The feature request is to be able, after the VM is created to modify the hardware, in this case the specified or all NICs
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 "me too" comments, 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.
The text was updated successfully, but these errors were encountered: