#289 migration from another basedn fails
Closed: Fixed None Opened 13 years ago by rcritten.

If you try to migrate from a basedn on one server to an IPA server it will fail.

I've found a couple of problems so far:

  • setting base_dn to * ends up defaulting to the IPA basedn
  • We always search for cn=ipaconfig to get the limits. The ldap2 client should be robust enough to forge ahead if we don't find this

I'm not sure if fixing both of these is going to do the trick but they need to be fixed before migration will work.


fix problems in ldap2 backend, migration plugin
freeipa-546-migration.patch

master: c298560

You can test this with 2 IPA servers on different machines with 2 different domains/realms.

On the server you'll be migrating from use ldapdelete to delete the dn:

cn=ipaconfig,cn=etc,dc=example,dc=com

Then on the other IPA server start migration:

ipa migrate-ds ldap://remote.example.com --user-container="cn=users,cn=accounts" --group-container="cn=groups,cn=accounts"

Metadata Update from @rcritten:
- Issue assigned to rcritten
- Issue set to the milestone: FreeIPA 2.0 - 2010/09

7 years ago

Login to comment on this ticket.

Metadata