Longhorn Upgrade test

Important

  • Since #10539 has been completed, we can rely on the test results of test_upgrade.py::test_upgrade to validate the upgrade process, instead of manually testing this case when the testing version >= v1.8

Setup

  1. 2 attached volumes with data. 2 detached volumes with data. 2 new volumes without data.
  2. 2 deployments of one pod. 1 statefulset of 10 pods.
  3. Auto Salvage set to disable.

Test

After upgrade:

  1. Make sure the existing instance managers didn’t restart.
  2. Make sure pods didn’t restart.
  3. Check the contents of the volumes.
  4. If the Engine API version is incompatible, manager cannot do anything about the attached volumes except detaching it.
  5. If the Engine API version is incompatible, manager cannot live-upgrade the attached volumes.
  6. If the Engine API version is incompatible, manager cannot reattach an existing volume until the user has upgraded the engine image to a manager supported version.
  7. After offline or online (live) engine upgrade, check the contents of the volumes are valid.
  8. For the volume never been attached in the old version, check it’s attachable after the upgrade.
[Edit]