Skip to content

Update the backup to 14.4

DJ Mountney requested to merge update-backup-14-4 into master

What does this MR do?

Fixes #2942 (closed) by updating the backup to 14.4, and the new backup has had a fix applied to set the trace artifacts expire_at field back to nil so they don't get cleaned up during the test.

Related issues

Closes: #2942 (closed)

How the backup was generated

  • I generate the backup by running a ci pipeline for the stable branch I want a backup for, in this case 5-4-stable
  • In that pipeline I cancel the qa jobs (but leave the spec tests) so that we don't get extra data in the backup
  • I let the spec tests finish. They will have installed the old backup, and migrated the instance to the version we want
  • Edit the gitlab-runner deployment replicas to 0, so the runner turns off
  • Login to the UI and delete the runner from the admin section. (This should help avoid cipher errors later)
  • Ensure the background migrations all complete, or go ahead and force them to https://docs.gitlab.com/ee/update/#checking-for-background-migrations-before-upgrading
  • I bounce the task-runner pod (this is so there is no existing tmp data, in order to keep the backup small)
  • I run a new backup from the bounced task-runner pod
  • I download the new backup from the ci minio
  • Rename and upload the backup to the proper location in our gcs

For this particular backup, I took a couple extra steps to fix the artifacts expired at

  • Scaled down the sidekiq runners prior to the spec tests running so the artifacts wouldn't be cleaned up
  • After the specs tests finished, I logged into the task runner, ran gitlab-rails console and updates all the artifact traces to have an expire_at set to nil. Then I continued with the other regular steps.

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

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 omnibus-gitlab opened
Edited by Jason Plum

Merge request reports