The documentation you're currently reading is for version 2.7.1. Click here to view documentation for the latest stable version.
When new versions of StackStorm are released, they are published to our APT and Yum repositories. You can use standard Linux package management tools to install these upgraded packages.
As part of the general upgrade procedure, you will need to run scripts to upgrade the Mistral Database prior to restarting StackStorm services. See below for more details. Depending on the versions you are upgrading to and from, you may need to run additional migration scripts.
If you skipped a version and are upgrading to a newer version, please make sure you also run the migration scripts for skipped versions.
General Upgrade Procedure¶
This is the standard upgrade procedure:
sudo st2ctl stop
Upgrade StackStorm packages using distro-specific tools:
sudo apt-get install --only-upgrade st2 st2web st2chatops st2mistral
sudo yum update st2 st2web st2chatops st2mistral
Upgrade Mistral database:
/opt/stackstorm/mistral/bin/mistral-db-manage --config-file /etc/mistral/mistral.conf upgrade head /opt/stackstorm/mistral/bin/mistral-db-manage --config-file /etc/mistral/mistral.conf populate | grep -v -e openstack -e keystone
The mistral and mistral-api services must be stopped at time of upgrade. If the services are restarted before the mistral-db-manage commands are run, then the
mistral-db-manage upgrade headcommand may fail.
Run the migration scripts (if any). See below for version-specific migration scripts.
Start StackStorm services:
sudo st2ctl start
Version-specific Migration Scripts¶
We document upgrade notes for the various versions. The upgrade notes section gives an idea of what major changes happened with each release. You may also want to take a look at the detailed Changelog for each version.
The following sections call out the migration scripts that need to be run when upgrading to the respective version. If you are upgrading across multiple versions, make sure you run the scripts for any skipped versions:
Node.js v6 is now used by ChatOps (previously v4 was used). The following procedure should be used to upgrade:
curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash - sudo apt-get install --only-upgrade st2chatops
curl -sL https://rpm.nodesource.com/setup_6.x | sudo -E bash - sudo yum clean all sudo rpm -e --nodeps npm sudo yum upgrade st2chatops
Extreme Workflow Composer users on RHEL or CentOS must run this command after upgrading packages:
sudo /opt/stackstorm/st2/bin/pip install --find-links /opt/stackstorm/share/wheels --no-index --quiet --upgrade st2-enterprise-auth-backend-ldap
This is a known issue, and will be resolved in a future release. This only applies to Extreme Workflow Composer users. It is not required for those using Open Source StackStorm.
The database schema for Mistral has changed. The executions_v2 table is no longer used. The table is being broken down into workflow_executions_v2, task_executions_v2, and action_executions_v2. After upgrade, using the Mistral commands from the command line such as
mistral execution-listwill return an empty table. The records in executions_v2 have not been deleted. The commands are reading from the new tables. There is currently no migration script to move existing records from executions_v2 into the new tables. To read from executions_v2, either use psql or install an older version of the python-mistralclient in a separate python virtual environment.
Please be sure to follow the general steps listed above to do the database upgrade.
If you’re seeing an error
event_triggers_v2 already existswhen running
mistral-db-manage upgrade head, this means the mistral services started before the mistral-db-manage commands were run. SQLAlchemy automatically creates new tables in the updated database schema and it conflicts with the mistral-db-manage commands. To recover, open the psql shell and delete the new tables manually and rerun the mistral-db-manage commands. The following is a sample script to recover from the errors.
sudo service mistral-api stop sudo service mistral stop sudo -u postgres psql \connect mistral DROP TABLE event_triggers_v2; DROP TABLE workflow_executions_v2 CASCADE; DROP TABLE task_executions_v2; DROP TABLE action_executions_v2; DROP TABLE named_locks; \q /opt/stackstorm/mistral/bin/mistral-db-manage --config-file /etc/mistral/mistral.conf upgrade head /opt/stackstorm/mistral/bin/mistral-db-manage --config-file /etc/mistral/mistral.conf populate sudo service mistral start sudo service mistral-api start
Datastore model migration - Scope names are now
st2kv.useras opposed to
We are piloting pluggable runners (See upgrade notes). Runners now have to be explicitly registered just like other content.
st2ctl restartand reload
st2ctl reloadare required after upgrade for the new pack management features to work properly. Some of the pack management actions and workflows have changed.
- Datastore model migration
In some cases, you may need to roll over the automation from one instance of StackStorm to another box or deployment. To do this, provision a new StackStorm instance, and roll over the content. Thanks to the “Infrastructure as code” approach, all StackStorm content and artifacts are simple files, and should be kept under source control.
- Install StackStorm
VERSION_NEWon a brand new instance using packages based installer.
- Package all your packs from the old
VERSION_OLDinstance and place them under some SCM like git (you should have done it long ago). Each pack must be in its own repo.
- Save your key-value pairs from the st2 datastore:
st2 key list -j > kv_file.json
- Grab packs from the SCM. If the SCM is git then you can directly install them with
st2 pack install <repo-url>=<pack-list>>
- Reconfigure all external services to point to the new StackStorm instance.
- Load your keys to the datastore:
st2 key load kv_file.json. You might have to adjust the JSON files to include
secretif you are upgrading from a version < 1.5. See migration script in
- Back up audit log from
VERSION_OLDserver found under
/var/log/st2/*.audit.logand move to a safe location. Note that history of old executions will be lost during such a transition, but a full audit record is still available in the log files that were transferred over.