This document describes the upgrade procedure for StackState.
There are several ways of upgrading StackState, depending on your configuration setup and the changes in the StackState release. Please read the StackState release notes carefully before starting an upgrade.
If you are using the StackState application and have not installed any StackPacks, or are using StackPacks that have not been upgraded in this release, follow these steps:
If you are using the StackState application, have installed StackPacks and are planning to upgrade one or more of them:
NOTE: when you upgrade a StackPack, any changes you have made to the templates in that StackPack will be overwritten.
Before upgrading StackState it is recommended to backup your configuration and topology data. The script
bin/sts-backup.sh will create a backup and store it inside the
NOTE: the StackState backup can only be restored in the StackState and StackPack versions prior to the upgrade.
StackPacks that are going to be upgraded must first be uninstalled. This removes all StackPack configuration from StackState.
NOTE: the StackPacks must be uninstalled using the version of StackState prior to the upgrade since this version can contain different installation logic from the new StackPack version.
Depending on your platform, you can use one of the following commands to upgrade StackState:
rpm -U <stackstate>.rpm
yum localinstall <stackstate>.rpm
dpkg -i <stackstate>.deb
apt-get upgrade <stackstate>.deb
StackPacks that have been upgraded can now be installed again. This provisions StackState with configuration information from the new StackPack.
Once StackState has been upgraded and started, verify that the new installation of StackState is reachable and that the application is running.
application_stackstate.conf. For detailed information check the configuring-the-ldap-authentication-server section.