New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DB now incompatible because not pinned in docker-compose.yml #106
Comments
I don't think we need to document DB upgrade procedure. Talking about the versions pinning. As I see in other files (CI), we only pin |
In hindsight, what I meant to say was "document the DB upgrade procedure as it relates to |
While it's true that the version of postgres doesn't matter.. if the major version bumps between the time the data directory was initialized, and the next invocation of |
@warrenvw That makes sense now! 👍 |
I'm still not sure this was the right approach. Usually the original problem reported may happen when:
The point is, all those are the docker practices, and completely separated from the context of StackStorm or st2-docker. If the |
As reported by @erick on #docker, postgres was not pinned in
docker-compose.yml
.https://stackstorm-community.slack.com/archives/C4QEPNE85/p1519237731000487
This lead to the situation where the DB (e.g. postgres) was initialized with what's now an incompatible version.
The simplest solution appears to be pinning each of
postgres
,mongo
,redis
andrabbitmq
.README.md
needs to be updated with information how to resolve any version incompatibilities (changing pinned version as required).If this is insufficient, then let's discuss below. Why is it insufficient? Do we need to go so far as to document the DB upgrade procedure as it relates to StackStorm?
The text was updated successfully, but these errors were encountered: