Read about some common errors users experience while deploying Salt minions using the SaltStack Config resource or the saltConfiguration property.

Delayed host startup

If Windows or Linux services on the host are not ready after you deploy your cloud template, you might receive a "Minion deployment and/or state file run failed" error in Cloud Assembly.

To resolve this error, upgrade the Master Plugin to the latest stable version. After you upgrade, you can enable a configuration setting in /etc/salt/master.d/raas.conf that allows Windows and Linux services time to become active before deploying the Salt minon.

After you upgrade to the latest version of the Master Plugin, complete these steps to delay host startup:

  1. Check the History tab on the deployment details page.
  2. If the error message says, "Minion deployment and/or state file run failed", copy the job ID (JID) and open SaltStack Config.
  3. In SaltStack Config, select Activity > Completed to open completed jobs.
  4. In the JID column, click the filter icon and type the JID.
  5. Click the JID to review the job results page.
  6. Click the Raw tab to see the raw output for the job.

    Windows

    If the last line in the raw output for the job contains "Failed to connect to host: timed out", you must add this configuration setting to /etc/salt/master.d/raas.conf to delay startup by 180 seconds: 
    sseapi_win_minion_deploy_delay: 180

    Linux

    If the line last in the raw output for the job contains "Remote host is not accessible using provided credentials", you must add this configuration setting to /etc/salt/master.d/raas.conf to delay startup by 90 seconds: 
    sseapi_linux_minion_deploy_delay: 90
  7. Restart the Salt master service:
    systemctl restart salt-master
  8. Re-deploy your cloud template.

    If the deployment was not successful, you can increase the delay parameter and re-deploy the template.

What to do next

To use the SaltStack Config capabilities to manage your resources, see the SaltStack Config documentation.