Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Bug 2039112 - pulp3 migration stats drastically underestimate migration times
Summary: pulp3 migration stats drastically underestimate migration times
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.9.7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: 6.9.9
Assignee: Ian Ballou
QA Contact: Cole Higgins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-11 02:04 UTC by Jessica Hanley
Modified: 2022-09-28 17:02 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-katello-3.18.1.52-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-20 20:34:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34497 0 Normal Closed pulp3 migration stats drastically underestimate migration times 2022-03-01 17:10:42 UTC
Red Hat Product Errata RHSA-2022:1478 0 None None None 2022-04-20 20:35:01 UTC

Description Jessica Hanley 2022-01-11 02:04:14 UTC 
Description of problem:

The customer ran "content migration-stats states" at the beginning of migration, and was given an estimate of 4 hours and 14 minutes:

# satellite-maintain content migration-stats
Running Retrieve Pulp 2 to Pulp 3 migration statistics
================================================================================
Retrieve Pulp 2 to Pulp 3 migration statistics:
============Migration Summary================
Migrated/Total RPMs: 0/236788
Migrated/Total errata: 0/332368
Migrated/Total repositories: 0/540

Estimated migration time based on yum content: 4 hours, 14 minutes

Note: ensure there is sufficient storage space for /var/lib/pulp/published to double in size before starting the migration process.
Check the size of /var/lib/pulp/published with 'du -sh /var/lib/pulp/published/'


The actual migration time was more than 14 hours.



Version-Release number of selected component (if applicable):

pulp2 in satellite 6.9


Actual results:

migration took more than 14 hours


Expected results:

migration time should have been close to the estimate of 4 hours and 14 minutes



Additional info:

This sounds similar to closed bz #1954820, but that was closed with an update for Satellite 6.9.4, whereas this issue is happening for a Satellite server running 6.9.7, and all of the packages on the Satellite server are newer than in the errata (RHBA-2021:2948).
Comment 4 Ian Ballou 2022-02-22 21:35:16 UTC 
Created redmine issue https://projects.theforeman.org/issues/34497 from this bug
Comment 5 Bryan Kearney 2022-02-23 00:04:59 UTC 
Upstream bug assigned to iballou
Comment 6 Bryan Kearney 2022-02-23 00:05:01 UTC 
Upstream bug assigned to iballou
Comment 7 Bryan Kearney 2022-03-01 20:04:55 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34497 has been resolved.
Comment 11 Griffin Sullivan 2022-03-23 16:15:33 UTC 
Verified in 6.9.9 snap 1

Content migration stats gives two separate values for migration time depending on hardware if the migration estimate is over 5 minutes.

Steps to Reproduce:
1. Sync rhel-7-server-rpms (and anything else you want)
2. # satellite-maintain content migration-stats

Expected Results:
Stats display two values that depend on hardware speed.

Actual Results:
Stats display two values that depend on hardware speed.

Output:
Running Retrieve Pulp 2 to Pulp 3 migration statistics
================================================================================
Retrieve Pulp 2 to Pulp 3 migration statistics: 
============Migration Summary================
Migrated/Total RPMs: 0/46731
Migrated/Total errata: 0/6918
Migrated/Total repositories: 0/5
Estimated migration time based on yum content, fast hardware, and low server load: 0 hours, 24 minutes
Estimated migration time based on yum content, slow hardware, and high server load: 1 hours, 36 minutes

Note: ensure there is sufficient storage space for /var/lib/pulp/published to double in size before starting the migration process.
Check the size of /var/lib/pulp/published with 'du -sh /var/lib/pulp/published/'

Note: ensure there is sufficient storage space for postgresql.
You will need additional space for your postgresql database.  The partition holding '/var/opt/rh/rh-postgresql12/lib/pgsql/data/'
   will need additional free space equivalent to the size of your Mongo db database (/var/lib/mongodb/).
                                                                      [OK]
--------------------------------------------------------------------------------
Comment 16 errata-xmlrpc 2022-04-20 20:34:53 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.9.9 Async Bug Fix Update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:1478
Note You need to log in before you can comment on or make changes to this bug.