[KUDU-1596] Automate upgrade/downgrade RC tests

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: test
• Assignee: Dinesh Bhat
• Reporter: Dinesh Bhat
• Created: 07/Sep/16 18:01
• Updated: 06/Mar/17 20:19

Description

In discussion with mpercy last week, we want to do the following to alleviate the tedious/manual release upgrade/downgrade tests.

• White box test cases, basic test to begin with.
  1. Create a table via external minicluster, say with 1.0 binaries
  2. Load data and shutdown the cluster
  3. SetBinarypath to new binaries(pre-existing location) carrying 1.1 version
  4. Restart the cluster with same parameters, key thing is to stash the RPC/webutil addresses so that we can restart the respective servers on same ports again.
  5. Add both negative and positive tests. Also need to see if we can induce an incompatible change by some means and test for negative cases.

• One way of doing it in Black Box mode:
  #version_test.py --release 0.9.1 --dir=<path to bins> --release 0.10.0 --dir=<path to bins>

1. Download 0.9.1
2. Unpack/Build 0.9.1
3. Run test ./bin/run-version-itest
4. Download 0.10.0
5. Unpack/Build 0.10.0
6. Run test ./bin/run-version-itest

Need to think how to pass around RPC/web endpoints, and how to introduce negative tests for incompatible test.

Issue Links

• blocks: KUDU-1500 TSAN race in ListTablets vs tablet metadata loading