Read some of the common errors that users experience during the SaltStack Config installation process and how to fix them.

Problem Cause Solution

The SaltStack Config user interface shows a 403 error or a blank screen.

When you first try to open SaltStack Config within vRealize Automation, nothing happens.

These symptoms might be caused if your vRealize Automation deployment is using a certificate signed by a non-standard certificate authority.

See Troubleshooting SaltStack Config environments with vRealize Automation that use self-signed certificates for a workaround.

When you first open the SaltStack Config in your vRealize Automation deployment, your web browser displays a security warning next to the URL or in the display page that the certificate cannot be validated.

These symptoms might be caused if your vRealize Automation deployment is using a certificate signed by a non-standard certificate authority.

See Troubleshooting SaltStack Config environments with vRealize Automation that use self-signed certificates for a workaround.

You see yum install error messages.

For example, when installing Salt as a pre-installation step (see Install or upgrade Salt), yum might return the following error:

[Error 14] curl#60 – “Peer’s Certificate issuer is not recognized.

In this case, it is likely that you are either experiencing DNS issues or you have a transparent TLS/https proxy in your environment.

To resolve DNS issues, ensure that repo.saltproject.io resolves on your machine or that you can reach that server.

If you have a transparent proxy, add sslverify=0 to the SaltStack yum repo configuration and then retry the installation of the packages. This will workaround the fact that your transparent proxy is interfering with connection certificates and TLS signatures.

The Salt master is not showing the keys for the minion.

Sometimes users experience a problem where minion IDs don’t appear when trying to get the Salt master to accept minion keys.

Specify the IP address of the Salt master in each minion’s etc/salt/minion.d/id.conf file.

Edit this file and change the master setting to show the Salt master’s IP address. For example, master:127.0.0.0.

For additional methods of connecting the minion to the Salt master, see Configuring the Salt Minion.

You experience authentication errors when applying a highstate.

During the initial application of the highstate to the first Salt master, you may see the following error message: Authenticationerroroccurred.

This error displays because the Salt master has not yet authenticated to the RaaS node.

The Master Plugin installation state will restart the Salt master service and the issue will be resolved automatically.