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 1929385 - pulp3: Improve migration re-run times if there were no or very little changes in pulp 2
Summary: pulp3: Improve migration re-run times if there were no or very little changes...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.9.0
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-16 18:47 UTC by Tanya Tereshchenko
Modified: 2021-04-21 13:10 UTC (History)
8 users (show)

Fixed In Version: pulp-2to3-migration-0.8.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:10:34 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 7779 0 Normal CLOSED - CURRENTRELEASE As a user, a migration re-run is very fast, if there were no or very little changes in pulp 2 2021-02-18 21:06:02 UTC
Red Hat Product Errata RHSA-2021:1313 0 None None None 2021-04-21 13:10:58 UTC

Description Tanya Tereshchenko 2021-02-16 18:47:54 UTC 
Description of problem:


### Motivation
Users run the migration task multiple times upfront, so the switchover to Pulp 3 happens quickly.
Switchover = stop pulp 2 services, run migration for the last time, start using pulp3.

### Existing concerns and thoughts

 * Following the same code path as normal migration when no changes have been made in pulp 2 takes a noticeable amount of time. We might need to introduce some shortcuts for the case when nothing has been changed in pulp 2.
 * Same goes to the case when only very few changes have been made.
 * If everything possible is done and no shortcuts are available we might need to look at the performance of the longest steps or rethink the approach.


Currently success depends on the amount of repositories (and not on content if it hasn't changed). The more Pulp 2 repositories are being migrated, the worse performance is. Dogfood has 40K repos, and re-run takes hours.
Comment 1 pulp-infra@redhat.com 2021-02-16 19:04:54 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 2 pulp-infra@redhat.com 2021-02-16 19:04:55 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2021-02-18 17:20:41 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2021-02-18 18:06:57 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 5 pulp-infra@redhat.com 2021-02-18 21:06:03 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 7 Lai 2021-03-12 20:31:09 UTC 
Steps to test:

1. Sync a couple small RH repos
2. Create cv and add repos from 1 to it
3. Publish
4. Run Migration
5. Once migration is completed, run migration again with no changes.
6. Once migration is completed, remove 1 repo from cv and republish.
7. Run migration again.

Expected result:
4. Should take the longest amount of time to finish
5. Should take the least amount of time to finish
7. Should take a few minutes to finish

Actual result:
4. Took 20 minutes to finish
5. Took under a minute to finish
7. Took ~3 minutes to finish

These were all done with a couple of small RH repos.  The run time can be seen under task.

python3-pulp-2to3-migration-0.9.1-1.el7pc.noarch

Verified on 6.9.0_017
Comment 10 errata-xmlrpc 2021-04-21 13:10:34 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 (Moderate: Satellite 6.9 Release), 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-2021:1313
Note You need to log in before you can comment on or make changes to this bug.