Pipelines in MRs targeting stable branches should use latest tag from the stable branch rather than the current release
As per the !7584 (comment 1910337914), pipelines that run as a part of an MRs which are merged into stable branches use tags prefixed with latest release.
This causes the upgrade tests to fail as the tag will be for e.g. 17.0.0-rfbranch.1290989414.08deb77e-0
but the code running in the MR will be related to the release in the stable branch. In this case the code running was 16.9
If we get the tag related to the release, upgrade-major
and upgrade-minor
will grab the right upgrade path and the test would pass.