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.
DescriptionJustin Sherrill
2019-03-18 17:34:48 UTC
Description of problem:
As part of content view publish/promote, we remove docker content from an docker existing docker repo in a lifecycle environment. For repos with large amounts of content, this can take a long time:
~300 docker manifests seems to take ~2 minutes
~2000 docker manifests seems to take ~30 minutes
Version-Release number of selected component (if applicable):
6.4.0
How reproducible:
Always
Steps to Reproduce:
1. Sync a docker repo: https://quay.io datawire/ambassador
2. Publish the docker repo in a CV
3. Re-publish the CV
Actual results:
Very slow
Expected results:
Should be fast
Additional info:
It appears that removing the docker manifests units in pulp is the slow piece
Comment 3pulp-infra@redhat.com
2019-03-18 19:31:40 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2019-03-18 19:31:41 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2019-03-27 20:31:42 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2019-04-03 13:10:52 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2019-07-09 03:22:43 UTC
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 8amacdona@redhat.com
2019-07-19 19:21:12 UTC
I am proceeding with a fix that won't require change katello changes.
There was some discussion about a potential workaround (https://pulp.plan.io/issues/4549#note-12) but that will not be necessary.
Comment 9pulp-infra@redhat.com
2019-07-29 18:01:23 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 10amacdona@redhat.com
2019-07-29 18:37:23 UTC
I have an open PR for this issue. 2 things need to be highlighted:
1. The patch (as a side effect) fixed a bug, so there will be a subtle behavior change. https://pulp.plan.io/issues/5181
2. The patch will increase memory usage for removal tasks. On the issue, I put up some numbers and recommend going forward with this patch: https://pulp.plan.io/issues/4549#note-17
Comment 11pulp-infra@redhat.com
2019-08-01 17:32:44 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 12pulp-infra@redhat.com
2019-08-01 18:02:45 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 13amacdona@redhat.com
2019-08-08 15:48:21 UTC
*** Satellite 6.5.2 Hotfix Available ***
1) Download pulp-docker-plugins-3.2.2-2.HOTFIXRHBZ1690070.el7sat.noarch.rpm from this bugzilla to your Satellite
2) Install:
rpm -Uvh pulp-docker-plugins-3.2.2-2.HOTFIXRHBZ1690070.el7sat.noarch.rpm
3) restart:
foreman-maintain service restart
4) resume operations
Comment 18pulp-infra@redhat.com
2019-09-25 21:02:11 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
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, 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-2019:3172