RaaS seems unstable after upgrading

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

You've just upgraded your Aria Config environment (RaaS daemon) and notice some strange behavior in Salt master connectivity, or job returns are missing

Environment

Aria Config  - all versions

Tanzu salt - all versions

Cause

Some versions of the RaaS daemon may introduce new configuration options or new default values for various options to help improve overall performance and reliability of the platform. There is no process that automatically updates the existing configuration with these options.

Resolution

1. Generate a new configuration file for the RaaS daemon as root
   1. su - raas -c "raas genconfig /etc/raas/new_config"
2. Compare the new configuration file stored in /etc/raas/new_config with /etc/raas/raas
   1. Do not attempt to create a diff file and then patch from this file. It may lead to bad options being introduced or kept.
3. Rename the /etc/raas/raas file to a backup file like /etc/raas/raas.`date +%Y%m%d%H%M%S`
   1. mv -v /etc/raas/raas /etc/raas/raas.`date +%Y%m%d%H%M%S`
4. Move /etc/raas/new_config to /etc/raas/raas
   1. mv -v /etc/raas/new_config /etc/raas/raas
5. Restart the RaaS daemon
   1. systemctl stop raas
   2. systemctl start raas

Additional Information

Some key changes throughout the RaaS daemon's history

* Change in authentication mechanism for Salt masters

* Change in default options for background workers

* Caching cycles

* Allow automatic history trimming via the keep_history settings

* Allow a login banner to be configured

* Allow monitoring via Prometheus and compatible systems

* Minion deployment tunable options