The [Batched Background Migration docs][0] say to finalize a migration
when two conditions are met:

1. The batched background migration is completed on GitLab.com
2. The batched background migration was added in or before the last required stop

Verify complete on GitLab.com
=================================

verified with chatops and details [here][1]

```
/chatops run batched_background_migrations status 1000544 --production
```

Verify [required stop][3]
=================================

The migration was was available in [`v17.1.0-ee`][2]

```
/chatops run release check https://gitlab.com/gitlab-org/gitlab/-/merge_requests/147220
```

`17.0` is a [required stop][4], and we are now on `17.2`, so I think we
might need to wait a bit...

MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/158720
resolves: https://gitlab.com/gitlab-org/gitlab/-/issues/471527
Changelog: removed

[0]:https://docs.gitlab.com/ee/development/database/batched_background_migrations.html#finalize-a-batched-background-migration
[1]:https://gitlab.com/gitlab-org/gitlab/-/work_items/462417
[2]:https://gitlab.com/gitlab-org/security/gitlab/-/tree/v17.1.0-ee
[3]:https://gitlab.com/gitlab-org/gitlab/-/blob/4ecb054fc7b57917e3f78cd0097925afddbf6aa2/config/upgrade_path.yml
[4]:https://docs.gitlab.com/ee/update/index.html#upgrade-paths