Description of problem: When doing the migration from Satellite 6.9 to Satellite 6.10, an important process is to migrate the content from Pulp2 to Pulp3, and currently, the way to monitor if the process was finished and/or still running is via the command "foreman-maintain content migration-stats" Based on the tests below, we can see the information it's not totally accurate. Version-Release number of selected component (if applicable): 6.9 How reproducible: 100% when the dataset is huge Steps to Reproduce: 1. Enable/Sync as immediate a huge # of repositories (about storage, something near 700GiB should be enough) 2. Start the migration 3. Actual results: The "foreman-maintain content migration-stats" will always be the same, independent of the pulp phase. I believe this will be updated only in the end. Expected results: The command be reflecting the current state of the migration Additional info:
Closing this BZ as WONTFIX. 6.9 is EOL and this is not an upgrade-blocking issue. Pulp 3 has changed drastically since we first calculated the estimation timing, so the experiments would need to be completely redone.