Bug 1848717

Summary:	Pulp 2 consumer erroneously returning empty yum applicability
Product:	Red Hat Satellite	Reporter:	Ian Ballou <iballou>
Component:	Pulp	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Bruno Rocha <rochacbruno>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	dkliban, jsherril, rchan, ttereshc
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-19 12:23:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ian Ballou 2020-06-18 19:58:06 UTC

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:

Comment 1 Justin Sherrill 2020-06-18 20:07:02 UTC

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

Comment 2 David Davis 2020-06-18 21:55:26 UTC

@ttereshc, any idea for how to reproduce this?

Comment 3 pulp-infra@redhat.com 2020-06-18 22:03:06 UTC

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

Comment 4 pulp-infra@redhat.com 2020-06-18 22:03:07 UTC

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

Comment 5 Tanya Tereshchenko 2020-06-19 11:42:56 UTC

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?

Comment 6 Ian Ballou 2020-06-19 12:23:10 UTC

@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 ***

Comment 7 Ian Ballou 2020-06-19 12:24:25 UTC

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