GitLab unexpectedly reports pending obsolete elastic migrations
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
Following a customer's upgrade to 16.3, it was noted that Elastic migrations were not running. The Rake task reported a list of new migrations, plus one Obsolete migration.
The customer provided the output more than once; and the reported migration was not consistent:
One of these migrations is from 14.3 and was removed in 15.0. This output was sure to be incorrect because the customer:
- Re-indexed entirely while running 15.x.
- Checked before upgrading 16.2 > 16.3 that all migrations were complete.
This has been observed by support before. Fix Hide obsolete migration warning when AS not set up (!137021 - merged) from %16.7 might resolve this, since it is related. It'd be useful to know if it's seen in %16.7 and later.
Issue raised so we can consolidate knowledge about this behaviour.
Workaround
See comment below.
Steps to reproduce
Unknown at this time.
Example Project
What is the current bug behavior?
GitLab erroneously reports obsolete migrations as outstanding.
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
16.3
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)