action #80726

[SLE][Migration] data migration from openldap2 -> 389-ds

Added by maritawerner over 2 years ago. Updated 8 months ago.

New test
Target version:
Start date:
Due date:
% Done:


Estimated time:


Support provided evidence to Engineering (including QA) that the test coverage for LDAP (openldap2 -> 389-ds) and Active Directory (samba et al) is not sufficient to cover our customers' most important scenarios - especially in the migration scenarios from older product major versions.

So this is a sub ticket to track and define migration scenarios that do a real data migration from LDAP to 389-ds to not only test that the tool itself works but also that the old data are move over.
More concrete scenarios need to be defind.

Tracker bug:


#1 Updated by maritawerner over 2 years ago

  • Description updated (diff)

#3 Updated by tjyrinki_suse about 2 years ago

  • Category set to New test

#4 Updated by maritawerner about 2 years ago

Pleae be aware that there is also a Jira ticket open for that and that the QE migration team is already doing some basic testing:

#5 Updated by coolgw almost 2 years ago

  • Assignee set to coolgw

#6 Updated by maritawerner over 1 year ago

Any update here? Wei Gao do you still work on that?

#7 Updated by coolgw over 1 year ago

maritawerner wrote:

Any update here? Wei Gao do you still work on that?

If we talk about 11sp4->15sp3 scenario, then i suppose we can close this topic since 11sp4 will out of service, so no action needed, could you help confirm this?

If we talk about 12/15 -> latest 15spx, then we block on following ticket: Core team has already trigger new module test case(running on 12spx, 15spx) but not implement with service check style.

#8 Updated by slo-gin 8 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Also available in: Atom PDF