Fresh installation of RAASversion 8.18.2, the RAAS server fails to display Master Plugins in the user interface.
The deployment highstate fails specifically at the import_initial_objects state.
Aria Automation Config 8.18.2
The failure occurs because the RAAS service cannot connect to the Redis cache during the initial content import.
The import_initial_objects task is responsible for loading startup content (e.g., test pings, example jobs). This task executes the following command: /usr/bin/raas dump --insecure --server https://localhost --auth root:salt --mode import < /tmp/sample-resource-types.raas
Investigation of /var/log/raas/raas revealed that the Redis service was using a configuration file located at /etc/redis/redis.conf, while the installation states were incorrectly placing the required Aria Config optimized configuration at /etc/redis.conf. Because the running Redis service was not using the correct configuration, the RAAS service could not establish a connection.
To resolve this issue, you must ensure the Redis service uses the configuration file provided by the Salt states. You can either manually move the file or update the state configuration.
Option 1: Update the Salt State (Recommended)
Modify the init.sls file to point to the correct directory used by the Redis service.
Locate the following file on your Salt Master: /sse-installer/salt/sse/eapi_cache/init.sls
Find the configure_redis section and update the name parameter to match the service's expected path:
YAML
configure_redis:
file.managed:
- name: /etc/redis/redis.conf # Change from /etc/redis.conf to /etc/redis/redis.conf
- source: salt://{{ slspath }}/files/redis.conf.jinja
Apply the highstate again: salt-call state.highstate
Option 2: Manual Configuration Alignment
If you prefer to manually align the files:
Copy the generated config to the correct location: cp /etc/redis.conf /etc/redis/redis.conf
Restart the Redis service: systemctl restart redis
Restart the RAAS service: systemctl restart raas