After patching a Red Hat Enterprise Linux (RHEL) 9.6 server hosting VMware Aria Config, the RaaS service fails to start or the UI does not load.
When you check the status of the Salt master using systemctl status salt-master, the service appears active, but the logs display "Connection refused" errors similar to the example below:
[root@ ~]# systemctl status salt-master
● salt-master.service - The Salt Master Server
Active: active (running)
...
Dec 14 21:37:50 salt-master[28972]: [ERROR ] Failed to get envs: [Errno 111] Connection refused
Dec 14 21:37:53 salt-master[28972]: [ERROR ] Failed to get the file listing for saltenv(base): [Errno 111] Connection refused
Dec 14 21:37:53 salt-master[29253]: [ERROR ] Failed to save events: [Errno 111] Connection refused
When you check the status of the RaaS daemon using systemctl status raas, the service appears active, but the logs display "Failed to connect to the storage backend" errors:
[root@ ~]# systemctl status raas
● raas.service - The SaltStack Enterprise API Server
Active: active (running)
...
Dec 14 21:42:38 raas[32605]: [CRITICAL] Failed to connect to the storage backend. Trying again in a bit.
Dec 14 21:42:39 raas[32605]: [CRITICAL] Failed to connect to the storage backend. Trying again in a bit.
VMware Aria Config 8.17 and lower
SaltStack (all versions)
Red Hat Enterprise Linux (RHEL) 9.6
This issue is caused by an incompatibility between the updated OpenSSL version included in RHEL patches and VMware Aria Config (RaaS) version 8.17 and lower.
To resolve this issue, upgrade the RaaS daemon (VMware Aria Config) to version 8.18.x or later.
Workaround If you are unable to upgrade VMware Aria Config immediately, ensure the server uses a compatible OpenSSL library version.
Revert or downgrade the OpenSSL package to version openssl-libs-3.0.1-47.