Reschedule migration to remove ultimate license from non-public projects
What does this MR do and why?
There was a bug in !88310 (merged) due to which the legacy ultimate license was not being removed from the projects when their visibility was changed from public to private. It has been fixed in affe032d.
This MR just reschedules an existing background migration.
Query plan
https://console.postgres.ai/gitlab/gitlab-production-tunnel-pg12/sessions/11114/commands/39910
Sample raw query
UPDATE "project_settings"
SET "legacy_open_source_license_available" = FALSE
WHERE "project_settings"."project_id" IN (SELECT "projects"."id"
FROM "projects"
WHERE "projects"."id" BETWEEN 10000 AND 15000
AND "projects"."visibility_level" != 20
AND "projects"."id" >= 10000
AND "projects"."id" < 10200)
Migration output
up
bin/rails db:migrate:up:main VERSION=20220722110026
WARNING: This version of GitLab depends on gitlab-shell 14.10.0, but you're running 14.9.0. Please update gitlab-shell.
main: == 20220722110026 RescheduleSetLegacyOpenSourceLicenseAvailableForNonPublicProjects: migrating
main: == 20220722110026 RescheduleSetLegacyOpenSourceLicenseAvailableForNonPublicProjects: migrated (0.0005s)
down
bin/rails db:migrate:down:main VERSION=20220722110026
WARNING: This version of GitLab depends on gitlab-shell 14.10.0, but you're running 14.9.0. Please update gitlab-shell.
main: == 20220722110026 RescheduleSetLegacyOpenSourceLicenseAvailableForNonPublicProjects: reverting
main: == 20220722110026 RescheduleSetLegacyOpenSourceLicenseAvailableForNonPublicProjects: reverted (0.0004s)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Closes #353225
Edited by Abdul Wadood