Description of problem: currently we default all repos (redhat and custom) to the on_demand default policy. This is problematic because common repos like epel, centos, and fedora all remove older versions of rpms. The result is that users will publish content views and will at some point in the future have broken content view version where an rpm is no longer available in the upstream repository but has not been downloaded yet (leading to 404s). We need to separate out the default for redhat and custom repos and default custom repos to on_demand
Connecting redmine issue https://projects.theforeman.org/issues/27367 from this bug
Proposing for 6.7 since the upstream issue will go into that and this needs docs for release notes
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27367 has been resolved.
ON_QA Verified @Satellite 6.7.0 snap 1.0 Steps/Observation: ___________________________________________________________________________________________________________________________________________________ hammer> repository create --name test2 --product Prod1 --organization-id 1 --url 'http://inecas.fedorapeople.org/fakerepos/zoo/' --content-type yum Repository created. hammer> repository info --id 22 ID: 22 Name: test2 Label: test2 Organization: Default Organization Red Hat Repository: no Content Type: yum Mirror on Sync: yes URL: http://inecas.fedorapeople.org/fakerepos/zoo/ Publish Via HTTP: yes Published At: http://qe-sat6-bm1./pulp/repos/Default_Organization/Library/custom/Prod1/test2/ Relative Path: Default_Organization/Library/custom/Prod1/test2 Download Policy: immediate <<<<<<<================================ 'Download Policy' Product: ID: 12 Name: Prod1 GPG Key: Sync: Status: Not Synced Created: 2019/11/16 11:05:51 Updated: 2019/11/16 11:05:53 Content Counts: Packages: 0 Source RPMS: 0 Package Groups: 0 Errata: 0 Module Streams: 0 ___________________________________________________________________________________________________________________________________________________
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:1454