Project

Profile

Help

Issue #2797

closed

Single consumer aplicability generation does not work unless profile already has applicability generated

Added by jsherril@redhat.com almost 7 years ago. Updated over 3 years ago.

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

Description

Recently the pulp team advised the katello team to start using the single consumer applicability generation api here:

POST /pulp/api/v2/consumers/UUID/actions/content/regenerate_applicability/

however this does not seem to work unless the profile has already been generated.

Steps to reproduce:

On a fresh pulp server (or a pulp server that has never had this consumer registered with its package profile):

a) sync a repository with errata (such as https://jlsherrill.fedorapeople.org/fake-repos/needed-errata/)
b) register a consumer, upload its package profile with some older package than what is in the repo with an errata (such as walrus 0.71)
c) bind the consumer to the repository
d) generate applicability using the api above
e) fetch applicability using:

POST /pulp/api/v2/consumers/content/applicability/ with body:

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

note that the list is empty. If you generate it using this api that we have been using for years it works fine:
POST /pulp/api/v2/consumers/actions/content/regenerate_applicability/

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

Note that once the profile is generated, it seems that the single consumer api seems to work fine.

Also available in: Atom PDF