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.
Description of problem:
The migration timing calculation performs an unnecessary "% 60", which can cause the timing to be much too low for large deployments that may take over 60 hours to complete the migration. The minutes are calculated correctly, but not the hours.
Version-Release number of selected component (if applicable):
Satellite 6.9 -- any version
How reproducible:
100% if the migration minutes is calculated to be over 3599
Steps to Reproduce:
1. Run the migration-stats command on a machine with enough repositories and RPMs to get the `migration_minutes` above 3599: https://gitlab.cee.redhat.com/satellite/katello/-/blob/SATELLITE-6.9.0/lib/katello/tasks/pulp3_migration_stats.rake#L21
2.
3.
Actual results:
The number of hours will be too low. For example, 3600 / 60 = 60. 60 % 60 = 0!
Expected results:
The number of hours to be correct.
Additional info:
verified on:
- tfm-rubygem-katello-3.18.1.54-1.el7sat.noarch
Fix is present in code.
Migration timing calculation looks good.
# satellite-maintain content migration-stats
Running Retrieve Pulp 2 to Pulp 3 migration statistics
================================================================================
Retrieve Pulp 2 to Pulp 3 migration statistics:
============Migration Summary================
.
.
.
Estimated migration time based on yum content, fast hardware, and low server load: 296 hours, 40 minutes
Estimated migration time based on yum content, slow hardware, and high server load: 1186 hours, 40 minutes
.
.
.
[OK]
--------------------------------------------------------------------------------
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.10 Async Security 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:8532
Comment 14Red Hat Bugzilla
2023-09-18 04:39:34 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days