summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorit33 <it33@users.noreply.github.com>2016-01-05 05:43:28 -0800
committerit33 <it33@users.noreply.github.com>2016-01-05 05:43:28 -0800
commit44dc4f2cac26dca6a88f1ed22b9729d640528768 (patch)
tree5fc4035e0215604e1fab1a405594999419595146 /doc
parent9f8d83dc268f95f1733e64b1296e7536b83fbd76 (diff)
downloadchat-44dc4f2cac26dca6a88f1ed22b9729d640528768.tar.gz
chat-44dc4f2cac26dca6a88f1ed22b9729d640528768.tar.bz2
chat-44dc4f2cac26dca6a88f1ed22b9729d640528768.zip
Update Upgrade-Guide.md
Diffstat (limited to 'doc')
-rw-r--r--doc/install/Upgrade-Guide.md19
1 files changed, 18 insertions, 1 deletions
diff --git a/doc/install/Upgrade-Guide.md b/doc/install/Upgrade-Guide.md
index edcc754f8..4480dedd2 100644
--- a/doc/install/Upgrade-Guide.md
+++ b/doc/install/Upgrade-Guide.md
@@ -36,6 +36,24 @@ If you're upgrading across multiple major releases, from 1.0.x to 1.2.x for exam
The following instructions apply to updating installations of Mattermost v0.7-Beta to Mattermost 1.1.
+## GitLab Mattermost Upgrade Troubleshooting
+
+#### Upgrading GitLab Mattermost when GitLab upgrade skips versions
+
+Mattermost is designed to be upgraded sequentially through major version releases. If you skip versions when upgrading GitLab, you may find a `panic: The database schema version of 1.1.0 cannot be upgraded. You must not skip a version` error in your `/var/log/gitlab/mattermost/current` directory. If so:
+
+1. Run `platform -version` to check your version of Mattermost
+2. If your version of the Mattermost binary doesn't match the version listed in the database error message, downgrade the version of the Mattermost binary you are using by [following the manual upgrade steps for Mattermost](/var/log/gitlab/mattermost/current) and using the database schema version listed in the error messages for the version you select in Step 1) iv).
+3. Once Mattermost is working again, you can use the same upgrade procedure to upgrade Mattermost version by version to your current GitLab version. After this is done, GitLab automation should continue to work for future upgrades, so long as you don't skip versions.
+
+| GitLab Version | Mattermost Version |
+|----------------|---------------------|
+| 8.1.x | v1.1.0 |
+| 8.2.x | v1.2.1 |
+| 8.3.x | v1.3.0 |
+
+## Upgrade Guide for Mattermost Beta Release
+
#### Upgrading Mattermost in GitLab 8.0 to GitLab 8.1 with omnibus
Mattermost 0.7.1-beta in GitLab 8.0 was a pre-release of Mattermost and Mattermost v1.1.1 in GitLab 8.1 was [updated significantly](https://github.com/mattermost/platform/blob/master/CHANGELOG.md#configjson-changes-from-v07-to-v10) to get to a stable, forwards-compatible platform for Mattermost.
@@ -48,7 +66,6 @@ The Mattermost team didn't think it made sense for GitLab omnibus to attempt an
Optionally, you can use the new [System Console user interface](https://github.com/mattermost/platform/blob/master/doc/install/Configuration-Settings.md) to make changes to your new `config.json` file.
-
#### Upgrading Mattermost v0.7.1-beta to v1.1.1
_Note: [Mattermost v1.1.1](https://github.com/mattermost/platform/releases/tag/v1.1.1) is a special release of Mattermost v1.1 that upgrades the database to Mattermost v1.1 from EITHER Mattermost v0.7 or Mattermost v1.0. The following instructions are for upgrading from Mattermost v0.7.1-beta to v1.1.1 and skipping the upgrade to Mattermost v1.0._