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:

A number of upstream users have reported that yum applicability doesn't work or stops working after some period of time on Katello 3.15 and beyond.  Here is the thread: https://community.theforeman.org/t/katello-3-15-doesnt-show-available-package-updates-anymore/18948/61

The fix was discovered to be an open (at the time of writing) Pulp 2 PR that relates to the attached Pulp 2 issue.  I have not been able to reproduce the issue, but the patch has reportedly fixed the problem for a number of users.

Version-Release number of selected component (if applicable):

Pulp 2.21.2

How reproducible:

I haven't been able to reproduce the issue, but many there is growing data about the problem in the thread above.  The Pulp 2 issue also provides some information about the failure.

Steps to Reproduce:

(To be discovered)

Actual results:

Failing applicability

Expected results:

Working applicability

Additional info:

We had a hard time reproducing this ourselves, so maybe the pulp team could help us come up with reproducer steps for QE?

@ttereshc, any idea for how to reproduce this?

The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Do we need a second BZ for the same bug? Or does this one have some special purpose?
Here is a BZ for the same bug with steps to reproduce https://bugzilla.redhat.com/show_bug.cgi?id=1847019
They are taken from the upstream issue.

Have you tried to generate applicability in pulp 2.21.1 or earlier and then try to retrieve it with 2.21.2?

@ttereshc I didn't realize there was already a bug for this, we can reject this one and add the 6.8 flag to the other.

The users who were reporting this issue were all on Pulp 2.21.2, so I didn't get a chance to try anything with the prior version.

*** This bug has been marked as a duplicate of bug 1847019 ***

Looks like the 6.8 flag is already there on the other bug.