Read about some errors you might encounter while configuring Automation Config and how to fix them.

Problem Cause Solution
You do not see the master key in the Pending tab in the Administration workspace in Automation Config. These symptoms might be caused for several reasons:
  • The sseapi_server value in the /etc/salt/master.d/cloud.conf file is incorrect. The cloud.conf file points to your Automation Config instance.
  • Your Salt master cannot communicate with Automation Config because it is still connected to your on-premises deployment. The sseapi_server value in the /etc/salt/master.d/raas.conf file takes precedence over the sseapi_server value in the cloud.conf file.
 Verify that the sseapi_server value in the cloud.conf file matches the ssc_url value for your region.

Verify that the sseapi_server value in the raas.conf file is commented out.

Re-run the sseapi-config join command.
You see access error messages after you run the sseapi-config join command.
CSP access token must have at least one of the following roles: 
[['csp:org_owner', 'csp:org_admin']]
 These symptoms might occur if you do not have the organization roles that are required to connect your Salt master to Automation Config. Contact your Organization administrator to assign you the required roles.
You see a command not found error message after you run the sseapi-config join command.
sseapi-config: command not found
 These symptoms might be caused if the sseapi-config command is not in your path. Check the /usr/local/bin directory for the sseapi-config command. If the command is there, add the /usr/local/bin directory to your path.