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.
Back in the 6.3 era we had a bug where the Pulp monthly maintenance was not being ran:
https://bugzilla.redhat.com/show_bug.cgi?id=1609928
We are seeing reports that GenerateApplicability performance seems to be worse in 6.6 so I did some digging. Part of the diagnosis routine for the above bug was to check the 2 collections and note if there was a significant size difference:
db.repo_profile_applicability
db.consumers
I've checked with an older customer 6.5 database and get the following counts:
> db.repo_profile_applicability.find().size()
61526
> db.consumers.find().size()
54726
>
Checking with another customer with similar sized database on 6.6 shows a greater than 10x ratio which was causing performance issues in older versions:
> db.repo_profile_applicability.find().size()
863830
> db.consumers.find().size()
66891
>
I checked and the montly maintenance is being ran and running it manually returns very quickly (5 seconds):
celery.worker.strategy:INFO: Received task: pulp.server.maintenance.monthly.queue_monthly_maintenance[5a5aefbd-dd52-42b5-8d38-2c3b65053f27]
celery.worker.strategy:INFO: Received task: pulp.server.maintenance.monthly.monthly_maintenance[7c4e5227-9572-439d-99e0-9ad938c9fc9c]
celery.app.trace:INFO: [5a5aefbd] Task pulp.server.maintenance.monthly.queue_monthly_maintenance[5a5aefbd-dd52-42b5-8d38-2c3b65053f27] succeeded in 0.0373372323811s: None
pulp.server.managers.consumer.applicability:INFO: [7c4e5227] Orphaned consumer profiles to process: 2253
pulp.server.managers.consumer.applicability:INFO: [7c4e5227] Orphaned consumer profiles processed: 2253
celery.app.trace:INFO: [7c4e5227] Task pulp.server.maintenance.monthly.monthly_maintenance[7c4e5227-9572-439d-99e0-9ad938c9fc9c] succeeded in 5.05477944389s: None
yet the size of repo_profile_applicability remains large.
On 3/23/20 9:07 AM, Tatiana Tereshchenko wrote:
> In 6.6, applicability calculation for modularity was introduced.
> It means that profile counter should be roughly doubled in comparison to
> the consumer one.
>
> A situation when the applicability profile is orphaned but not cleaned
> up is when consumer system has changes in RPMs installed but not in
> modules and vice versa.
> I wouldn't expect this to happen that often so the numbers of
> applicability increases that much, except the non-modular repositories
> case which should be handled separately.> On the system which you shared, there are many modular applicability
> profiles for consumers with no modularity content, maybe this case is
> not handled correctly during the clean up stage.
>
Comment 4pulp-infra@redhat.com
2020-03-28 12:53:34 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2020-03-28 12:53:35 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2020-05-08 19:30:40 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2020-05-08 22:14:11 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 11pulp-infra@redhat.com
2020-05-19 14:31:52 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 12pulp-infra@redhat.com
2020-05-19 16:32:42 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 (Important: Satellite 6.7.4 Async Bug Fix 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-2020:4127
Comment 23Red Hat Bugzilla
2023-09-15 00:30:31 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days