Bug 2039112

Summary:	pulp3 migration stats drastically underestimate migration times
Product:	Red Hat Satellite	Reporter:	Jessica Hanley <jhanley>
Component:	Repositories	Assignee:	Ian Ballou <iballou>
Status:	CLOSED ERRATA	QA Contact:	Cole Higgins <chiggins>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.9.7	CC:	iballou, juwatts, osousa
Target Milestone:	6.9.9	Keywords:	Triaged, Upgrades
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	tfm-rubygem-katello-3.18.1.52-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-20 20:34:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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