Project

General

Profile

Actions

Bug #35079

closed

Pulp 3 migration stats timing is too low for very large deployments

Added by Ian Ballou over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Repositories
Difficulty:
easy
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2098221

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):

Katello 3.18

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 in the migration-stats rake task.
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:

Actions #1

Updated by Ian Ballou over 2 years ago

  • Subject changed from Pulp 3 migration stats timing is too low for very large deployments to Pulp 3 migration stats timing is too low for very large deployments
  • Assignee set to Ian Ballou
  • Target version set to 3.18-no-release-planned
  • Difficulty set to easy
Actions #2

Updated by The Foreman Bot over 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/10170 added
Actions #3

Updated by Chris Roberts over 2 years ago

  • Triaged changed from No to Yes
Actions #4

Updated by Ian Ballou over 2 years ago

  • Status changed from Ready For Testing to Closed
  • Fixed in Releases 3.18-no-release-planned added
Actions

Also available in: Atom PDF