Finalize delete orphaned deployments background migration
What does this MR do?
After the re-rescheduled BG migration, we've confirmed that all of the jobs are succeeded.
- Kibana: https://log.gprd.gitlab.net/goto/5b817ef73ca093171421ae8afeecd9be
- Tracking:
[ gprd ] production> Gitlab::Database::BackgroundMigrationJob.where(class_name: 'DeleteOrphanedDeployment
s').pending.count
=> 0
[ gprd ] production> Gitlab::Database::BackgroundMigrationJob.where(class_name: 'DeleteOrphanedDeployment
s').succeeded.count
=> 16638
This is ready for proceeding to finalizing according to the BG migration process.
Related #335071 (closed)
Migration
shinya@shinya-B550-VISION-D:~/workspace/thin-gdk/services/rails/src$ tre bin/rails db:migrate:redo VERSION=20211011152701
INFO: This script is a predefined script in devkitkat.
WARNING: This version of GitLab depends on gitlab-shell 13.21.1, but you're running 13.21.0. Please update gitlab-shell.
WARNING: This installation of GitLab uses a deprecated syntax for 'config/database.yml'. The support for this syntax will be removed in 15.0. More information can be found here: https://gitlab.com/gitlab-org/gitlab/-/issues/338182
== 20211011152701 CleanupDeleteOrphanedDeploymentsBackgroundMigration: reverting
== 20211011152701 CleanupDeleteOrphanedDeploymentsBackgroundMigration: reverted (0.0000s)
== 20211011152701 CleanupDeleteOrphanedDeploymentsBackgroundMigration: migrating
== 20211011152701 CleanupDeleteOrphanedDeploymentsBackgroundMigration: migrated (0.0189s)
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
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
Edited by Shinya Maeda