- Home
- Migration Guide
- Tool Migration
- Migration Tool Release Notes
- Migration Tool 1.5.1
Migration Tool 1.5.1#
Release Date: 17 November 2026
Addressed Issues#
-
[MSRH-1830] Fixed an issue wherein, when the migration tool skipped a team during the project members migration and revoked the access that an earlier run had granted to that team, it could also remove the access of another team that uses the same LDAP group on the same project. The tool now keeps the access of the other team. In addition, a dry run (
DRY_RUN) no longer saves the resolved LDAP group names toldap_group_state.json, so a later run does not rely on groups that were never created. -
[MSRH-1730] Fixed an issue wherein the Migration Tool did not remove an outdated LDAP group from MSR 4 after a migration run renamed the group, if the outdated group name was recorded for more than one team. As a result, MSR 4 could map LDAP users to the outdated group, which had no project grants, rather than to the renamed group, and the users lost the project access that the migration granted. The issue occurred when the same LDAP group backed teams in multiple organizations and either of the following took place:
- A CN collision appeared after a migration run that named the group after its CN.
- The group naming format changed while a CN collision existed.
The Migration Tool now deletes the outdated group when no team uses it and it has the same LDAP DN as the current group.
-
[MSRH-1560] Fixed an issue wherein the project members migration step, when run in granular mode with MSR 4 on LDAP authentication, failed and no team's organization-wide access was migrated in that run. The step failed with the following error:
null value in column "entity_id" of relation "project_member" violates not-null constraintThe issue occurred when a team that is not synced from LDAP had only organization-wide access in MSR 2 or MSR 3. The migration tool now skips the organization-wide access of that team with a warning and migrates the access of the other teams.
-
[MSRH-1543] Fixed an issue wherein rerunning the projects migration step after turning off per-repository replication rules left those rules in MSR 4 alongside the new per-project rules, which caused each repository to replicate twice. The projects migration step now removes the replication rules that the current settings no longer generate and retains unchanged rules along with their replication history. Rerunning the step with per-repository rules turned on no longer resets their replication history. Previously replicated images are unaffected.