Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 2040811

Summary:	"foreman-maintain content migration-stats" it's not accurate.
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Satellite Maintain	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.9.8	CC:	apatel, iballou, kgaikwad, mkalyat, pdwyer, rcavalca, swachira
Target Milestone:	Unspecified	Keywords:	Triaged, Upgrades, UserExperience
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-07-14 14:01:41 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 Waldirio M Pinheiro 2022-01-14 18:18:48 UTC

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:

Comment 4 Ian Ballou 2023-07-14 14:01:41 UTC

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.