If running a SSM clustered system, there is a certain procedure to follow when upgrading SSM
If the following process is not followed, the SSM services can reboot repeatedly until the database reconfigures itself. This can take a long time to resolve (a day in some cases) or it can even stay in this state.
To upgrade a SSM Clustered system:
- take a backup from each SSM server
- stop the SSM services on each server
- upgrade SSM servers
- upgrade clients to the same version
- reboot each server
- log into client to confirm the upgrade