Skip to content

Makes 14.9 a required upgrade before moving to 14.10

DJ Mountney requested to merge make-14.9-required into 14-10-stable

What does this MR do?

Makes 14.9 a required step on the upgrade path to 14.10. 14.10 includes a migration that fails unless a background migration from 14.9 has been completed. This has already been added to our docs at https://docs.gitlab.com/ee/update/index.html#14100 and https://docs.gitlab.com/ee/update/index.html#upgrade-paths

Customer impact

The majority of self-managed customers have not yet upgraded to 14.9 https://app.periscopedata.com/app/gitlab/406972/Version-Upgrade-Rate?widget=8658008&udv=0 and are likely to try and skip 14.9 to go to 14.10 and run into the errors that this merge request prevents.

Customers who run into this have their installation fail during migrations. And need to rollback to their previous installed version and upgrade to 14.9 before proceeding. If customers were following our downgrade https://docs.gitlab.com/ee/update/package/downgrade.html instruction, this would also include having them restore from backup.

Related issues

Part of #6864 (closed)

Related to gitlab!83918 (closed)

Test Plan

Docker

  1. Run GitLab 14.8 via the docker image, and use volumes to persist data across restarts/upgrades
  2. Upgrade to this branch's docker image and see the container fail during startup due to the version requirement
  3. Upgrade to 14.9's docker image (wait for background migrations to complete if you want the following upgrade to fully work, or don't wait if you just want to see it get to the reconfigure step)
  4. Upgrade once again to this branch's docker image, and this time the container should start fine.

Package

  1. Install 14.8 package
  2. Attempt to upgrade to this branch, and see the preupgrade fail
  3. Upgrade to 14.9 (wait for background migrations to complete if you want the following upgrade to fully work, or don't wait if you just want to see it get to the reconfigure step)
  4. Upgrade to this branch

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

  • Merge Request Title, and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com
  • Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
  • trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for the GitLab Chart opened
Edited by DJ Mountney

Merge request reports