Project

Profile

Help

Issue #2793

closed

applicable rpms only show up if at least one errata is applicable

Added by jsherril@redhat.com about 7 years ago. Updated about 5 years ago.

Status:
CLOSED - WORKSFORME
Priority:
High
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.12.2
Platform Release:
OS:
CentOS 7
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Steps to reproduce:

1) Register a consumer
2) create and sync a yum repository without errata (such as centos7 updates http://mirror.centos.org/centos/7/updates/x86_64/)
3) bind the consumer to repo 2)
4) ensure that at least one package is older than is available (such as running 'yum downgrade screen')
5) generate repo applicability using the call:

POST /pulp/api/v2/consumers/actions/content/regenerate_applicability/ with body:

{ 'consumer_criteria' : { 'filters' : { 'id' : { '$in' : [UUID] } } } }

6) fetch applicable rpm ids:
/consumers/content/applicability/

{
'criteria' : { 'filters' : { 'id' : { '$in' : [UUID] } } },
'content_types' : ['rpm']
}

The list will be empty. However if you then

7) create a new repo with errata (https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/), sync it
8) bind that repo to the consumer
9) install the older version of walrus (0.71)
10) trigger applicability generation in the same way
11) fetch applicable rpm ids again

you'll see that now walrus AND the needed centos rpms are showing as applicable. The rpms applicable from the 2nd repo have nothing to do with the first repo. It seems like maybe pulp is ignoring all applicable rpms if no errata are applicable.

Also available in: Atom PDF