I recently upgraded my LCM deployed SSC server to 8.8. If you need a guide to go through the upgrade you can find my other post here.
After the upgrade was completed i was noticing strange behavior in the SSC UI so i checked the status the of the services. Here are the errors i found and how i fixed them
The first step was to check the status of the service
systemctl status salt-master
The return was this
* salt-master.service - The Salt Master Server
Loaded: loaded (/lib/systemd/system/salt-master.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-05-16 03:32:35 UTC; 6s ago
Docs: man:salt-master(1)
file:///usr/share/doc/salt/html/contents.html
https://docs.saltproject.io/en/latest/contents.html
Main PID: 4577 (salt-master)
Tasks: 39 (limit: 9830)
Memory: 335.0M
CGroup: /system.slice/salt-master.service
|-4577 /bin/python3 /usr/bin/salt-master
|-4581 /bin/python3 /usr/bin/salt-master
|-4589 /bin/python3 /usr/bin/salt-master
|-4593 /bin/python3 /usr/bin/salt-master
|-4602 /bin/python3 /usr/bin/salt-master
|-4606 /bin/python3 /usr/bin/salt-master
|-4608 /bin/python3 /usr/bin/salt-master
|-4609 /bin/python3 /usr/bin/salt-master
|-4616 /bin/python3 /usr/bin/salt-master
|-4697 /bin/python3 /usr/bin/salt-master
|-4699 /bin/python3 /usr/bin/salt-master
|-4703 /bin/python3 /usr/bin/salt-master
|-4711 /bin/python3 /usr/bin/salt-master
|-4712 /bin/python3 /usr/bin/salt-master
|-4713 /bin/python3 /usr/bin/salt-master
|-4714 /bin/python3 /usr/bin/salt-master
|-4715 /bin/python3 /usr/bin/salt-master
`-4717 /bin/python3 /usr/bin/salt-master
May 16 03:32:34 ssc-01a.corp.local systemd[1]: Starting The Salt Master Server...
May 16 03:32:35 ssc-01a.corp.local salt-master[4577]: [WARNING ] /usr/lib/python3.7/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.25.11) or chardet (4.0.0) doesn't match a supported version!
May 16 03:32:35 ssc-01a.corp.local salt-master[4577]: RequestsDependencyWarning)
May 16 03:32:35 ssc-01a.corp.local systemd[1]: Started The Salt Master Server.
The way i got around the error was by running
pip3 install --upgrade requests
Alternatively the official documentation is here talks about extracting the .whl file from the my vmware customer connect portal here. The file we are looking for is vRA_SaltStack_Config-8.8.0.7-1_Installer.tar.gz
Once Downloaded we are looking for SSEAPE-8.8.0.7-py2.py3-none-any.whl found under sse-installer/salt/sse/eapi_plugin/files
The file needs to be uploaded on the node having the issue and we would run
sudo pip3 install SSEAPE-8.8.0.7-py2.py3-none-any.whl --prefix /usr
Finally we can restart the saltstack service and verify that its running without errors:
* salt-master.service - The Salt Master Server
Loaded: loaded (/lib/systemd/system/salt-master.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2022-05-15 20:02:56 UTC; 51s ago
Docs: man:salt-master(1)
file:///usr/share/doc/salt/html/contents.html
https://docs.saltproject.io/en/latest/contents.html
Main PID: 31309 (salt-master)
Tasks: 39 (limit: 9830)
Memory: 330.0M
CGroup: /system.slice/salt-master.service
|-31309 /bin/python3 /usr/bin/salt-master
|-31315 /bin/python3 /usr/bin/salt-master
|-31320 /bin/python3 /usr/bin/salt-master
|-31323 /bin/python3 /usr/bin/salt-master
|-31325 /bin/python3 /usr/bin/salt-master
|-31326 /bin/python3 /usr/bin/salt-master
|-31327 /bin/python3 /usr/bin/salt-master
|-31328 /bin/python3 /usr/bin/salt-master
|-31330 /bin/python3 /usr/bin/salt-master
|-31397 /bin/python3 /usr/bin/salt-master
|-31398 /bin/python3 /usr/bin/salt-master
|-31400 /bin/python3 /usr/bin/salt-master
|-31411 /bin/python3 /usr/bin/salt-master
|-31412 /bin/python3 /usr/bin/salt-master
|-31413 /bin/python3 /usr/bin/salt-master
|-31414 /bin/python3 /usr/bin/salt-master
|-31415 /bin/python3 /usr/bin/salt-master
`-31416 /bin/python3 /usr/bin/salt-master
May 15 20:02:54 ssc-01a.corp.local systemd[1]: Starting The Salt Master Server...
May 15 20:02:56 ssc-01a.corp.local systemd[1]: Started The Salt Master Server.
If the status page a return similar to this
sseapi_rpc_queue: could not connect to SSE server
Follow my other guide here