RPM Support

Issue #2793

Updated by jsherril@redhat.com almost 7 years ago

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: 
 <pre> 
 { ```{ 'consumer_criteria' : { 'filters' : { 'id' : { '$in' : [UUID] } } } } 
 </pre> }``` 

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

 ```{ 
 <pre> 
 { 
 'criteria' : { 'filters' : { 'id' : { '$in' : [UUID] } } }, 
 'content_types' : ['rpm'] 
 } 
 </pre> }``` 

 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.

Back