Skip to content

Do not auto upgrade database if attributes missing

Robert Marshall requested to merge 6518-do-not-check-upgrade-if-no-attributes into master

What does this MR do?

For some first installations, or when the public attributes files are in a weird state, Omnibus GitLab will attempt to run an automatic pg_upgrade.

This adds a new feature of GitlabCtl::Util that checks for the file's existence and then uses that to gate automatic database upgrades.

Related issues

Closes #6518 (closed)

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