Using VMware Tools to deploy salt-minion does not work in an isolated or air gapped environment
Article ID: 405985
Updated On:
Products
Issue/Introduction
The environment was configured as per documentation: Enable Salt Minion Using VMware Tools
However the installation is failing with status code 130, reported in VM parameter guestinfo.vmware.components.salt_minion.laststatus.
The same status code can be found for environments using a solution provided by the VMware Professional Service Offering (PSO) and may result into VM deployments failing with error code 130. The relevant Orchestrator workflow would show several logs "Salt minion deployment status is: 130" e.g.:
The VM where the salt-minion is to be installed has limited or no access to the Internet.
Configuring source parameter in the configuration file tools.conf does not avert the situation.
Environment
- Aria Automation Config
- VMware Tools
- Aria Automation
Cause
The VMware Tools installation script does require a connection to the online Repository at packages.broadcom.com
Resolution
Different workarounds are available, depending on the chosen installation method:
- Using the source parameter from command line, a different/local Repository server can be used
- Using Aria Automation the salt-minion can be deployed as part of the VM deployment: Add the Salt minion to deployments in air-gapped environments
Additional Information
The latest version of the svtminion script can be found here: https://github.com/saltstack/salt-vmtools
Feedback
