[HDDS-6633] Refactor upgrade acceptance tests to reduce code duplication

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Labels: pull-request-available
• Assignee: Ethan Rose
• Reporter: Ethan Rose
• Created: 22/Apr/22 15:00
• Updated: 27/May/23 16:57
• Resolved: 28/Mar/23 22:38

Description

The upgrade/downgrade acceptance tests currently duplicate tests between the callbacks for each set of version upgrades. We can extract these common tests to a different area where they run for upgrade/downgrade tests of all versions. Other improvements to handle as part of this Jira include:

• Not requiring TEST_DIR variable to be set to manually run a cluster for testing purposes
• Updating the Ozone release guidelines to specify that the whole upgrade test matrix must be run manually before releasing, because CI will only test upgrade/downgrade from the last release to save time.

Issue Links

• blocks: HDDS-8239 Backwards compatibility fix for new RATIS_DATASTREAM port
• causes: HDDS-8375 Fix typos in upgrade acceptance test README
• relates to: HDDS-8711 Intermittent timeout of Prepare Ozone Manager in upgrade acceptance test
• split to: HDDS-8305 Consider removing load.sh from Upgrade acceptance test code
• links to: GitHub Pull Request #4456