14.5 Migration UpdateVulnerabilityOccurrencesLocation does not mark itself as complete
Test added in !83164 (diffs) demonstrates that this migration does not mark itself as complete after execution.
Jobs spawned during its execution will permanently remain in pending
state.
Steps to reproduce
- Install a new GitLab 14.4 EE omnibus instance
- Add an ultimate license to the instance
- Create a project with some vulnerabilities in its dependencies and run GitLab's SAST jobs over it to detect those vulnerabilities (using a Runner, any version)
- Upgrade it to 14.5 to invoke the 14.5 background migration: !72788 (merged)
- Check pending background migrations count: https://docs.gitlab.com/ee/update/#checking-for-background-migrations-before-upgrading
- Expectation: Count is non-zero
- Observation: Count is 1+
Edited by Harsh Chouraria