Ensure that an instance with non-last schema is operational #240
Description
We always test Tarantool with a last version of a schema, but never test that a non-upgraded instance works correctly. However a non-upgraded state is usual when one updates Tarantool to a new version in a replication cluster. If Tarantool is not operational in this state it means that the update w/o downtime is not possible. We have at least two bugs related to pure testing of upgrade scenarios:
- Can not start after upgrade schema tarantool#3652
- Ambigous behavior when upgrading schema from 1.6 to 1.7, 1.9 or 1.10 tarantool#3591
To mitigate this we need to implement two options in test-run.py that allows to specify snapshot used by Tarantool to bootstrap and option to disable schema upgrade.
Original idea described in a similar ticket in a Tarantool repository -
tarantool/tarantool#4801