if migration data contains replication conflicts, ipa-migrate tries to still add them to the deployment we are migrating to, but fails with 389ds error
inproper tool behavior
ipa-server-4.12.2-24.el10_1.1.x86_64
always
conflict entries are handled by the ipa-migrate and skipped
ipa-migrate tries to add them and fails:
Failed to add "idnsname=23.3.10.in-addr.arpa.+nsuniqueid=0acc7201-b02311f0-95b88e22-54950682,cn=dns,$suffix" error: Invalid DN syntax: illegal attribute in RDN
copy of https://issues.redhat.com/browse/RHEL-153857
PR: https://github.com/freeipa/freeipa/pull/8226
master:
ipa-4-12:
Metadata Update from @frenaud: - Custom field rhbz adjusted to https://redhat.atlassian.net/browse/RHEL-153857
ipa-4-13:
Metadata Update from @frenaud: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
The patch introduced a regression in test_integration/test_ipa_ipa_migration.py::TestIPAMigratewithBackupRestore::test_ipa_migrate_stage_mode, re-opening.
test_integration/test_ipa_ipa_migration.py::TestIPAMigratewithBackupRestore::test_ipa_migrate_stage_mode
Test logs (internal url): https://$ARTIFACTS_SERVER/idm-ci/freeipa_upstream_nightly/Nightly-latest-testing-repo-selinux/master/2026-03-18_17-10/latest-testing-repo-selinux/test_IPAMigrate_backuprestore/2/report.html?sort=result
Metadata Update from @frenaud: - Issue status updated to: Open (was: Closed)
New PR: https://github.com/freeipa/freeipa/pull/8263
@frenaud please review and close the issue if it is ready now.