After you have successfully upgraded the RaaS node, you can then upgrade any Salt masters that use the Master Plugin to connect to SaltStack Config.


Before you upgrade the Salt master(s), ensure that the pip3 application is installed on the Salt masters. If you are upgrading from the latest version of the Master Plugin, this application is already installed.

To upgrade the Master Plugin on a Salt master:

  1. Stop the salt-master service using the following command:
    sudo systemctl stop salt-master
  2. Check which version of Python is running on the Salt master. If it is running Python 3.6 or higher, no changes are needed. Otherwise, delete the prior version of the SSEAPE module. (The SSEAPE is the SaltStack Config plugin for the Salt master). For example:


    sudo rm -rf /usr/lib/python3.6/site-packages/SSEAPE*


    sudo rm /usr/lib/python3.6/dist-packages/SSEAPE*
  3. Upgrade the Master Plugin by manually installing the updated Python wheel. Use the following example commands, replacing the exact name of the wheel file:


    sudo pip3 install SSEAPE-file-name.whl --prefix /usr


    sudo pip3 install SSEAPE-file-name.whl

    Some users might need to alter the syntax to pip3.6 or pip36 for their operating systems.

  4. Update the API (RaaS) module paths by editing the /etc/salt/master.d/eAPIMasterPaths.conf file to reference the paths to the various modules. For example, you might change all python2.7 references in this file to python3.6.

    Depending on how you initially installed SaltStack Config, the eAPI Salt master paths could instead be in the /etc/salt/master.d/raas.conf file instead.

  5. Check the engines section in /etc/salt/master.d/raas.conf to confirm that it matches the following:
      - sseapi: {}
      - eventqueue: {}
      - rpcqueue: {}
      - jobcompletion: {}
      - keyauth: {}

    If a problem occurred, you may need to restore your backups of the /etc/salt/master.d/raas.conf and /etc/salt/master.d/eAPIMasterPaths.conf files.

  6. If you are using the salt-master key authentication (recommended), make sure that the sseapi_pubkey_path is configured and that sseapi_username and sseapi_password are commented out in /etc/salt/master.d/raas.conf.
    sseapi_pubkey_path: /etc/salt/pki/master/
  7. Check that the master_job_cache and event_return entries are set to sseapi. The pgjsonb returner is no longer available.
  8. Start the salt-master service with the following command:
    sudo systemctl start salt-master

The upgrade process is now complete. If you encounter any other errors, refer to the Troubleshootingpage or Contact Support.