RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2495

The ipa migrate-ds performs migration without any output about the following information: 
 * How many entries are loaded so far
 * How many entries were not loaded due to errors
 * How much time did it take

I suggest we add a parameter, for example --stats=<number> where number denotes number of entries after which to report the statistics. For example --stats=1000 will output statistics every 1000 entries. The output might look like something like this:
{{{
Chunk, Entries, Time, Success, Failure
1, 1000, 5.34, 934, 66
2, 1000, 5.03, 891, 109
3, 389, 2.71, 380, 9
}}}

The output can be easily then put into the Calc and analyzed. We would be able to see: the process of load (that it is doing something), whether the the load slows down, whether it is successful and so on. Such stats will be very valuable during pilot and product evaluation when admin assesses what it would take to migrate to IPA.

Thanks for the report. Adding continuous migration status to the "ipa migrate-ds" command is not practical, as IPA commands return after they are completed (i.e. migration finishes).

However, Bug 904119 added continuous logging to /var/log/httpd/error_log, where one can track the progress of migration. If this is not sufficient, please file RFE for improving this log file.