Applicable versions: 6.1.0, 6.2.0
This article explains how to troubleshoot and resolve an "Error getting raas lock" error message, various HTTP 401 and 403 responses, and potential other errors related to a master-to-raas connection.
A message like the following is appearing in the salt master logs, possibly frequently.
2020-02-04 12:57:27,155 [sseape.utils.init_pubkey:57 ][ERROR ] Error getting raas lock.
This issue is typically caused by a mismatch between the public key being used by the master to authenticate to SaltStack Enterprise and the public key that has been accepted in SaltStack Enterprise for that master.
- Stop the salt master:
systemctl stop salt-master
- On the salt master, remove the public key for SSE authentication:
- In SSE, under "Administration"/"Master Keys" ("System Administration"/"Master Keys" in 6.1.0) delete the key for the associated master:
- Start the salt master:
systemctl start salt-master
- In SSE, the new master key will show up in Pending; accept it: