Fix PG::ForeignKeyViolation: ERROR: insert or update on table "services"
requested to merge 198738-activerecord-invalidforeignkey-pg-foreignkeyviolation-error-insert-or-update-on-table into master
What does this MR do?
To avoid ForeignKeyViolation errors, we should check if at the time background migration job is executed scheduled record still exists in a database. Each record is processed in separate sidekiq job, so this errors does not blocks migration from completing, however they may cause unnecessary confusion.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Closes #198738 (closed)
Edited by 🤖 GitLab Bot 🤖