Bug 1732056

Summary:	[RFE] custom repositories should default to immediate
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	Repositories	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED ERRATA	QA Contact:	vijsingh
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.7.0	CC:	pcreech, spetrosi, trichard
Target Milestone:	6.7.0	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Satellite 6.7 uses separate settings to configure default download policies for Red Hat and custom repositories: `Default Red Hat Repository download policy` and `Default Custom Repository download policy`. The default value for the `Default Red Hat Repository download policy` setting is `on_demand`. The default value for the `Default Custom Repository download policy` setting is `immediate`. These settings affect newly synchronized repositories. To review the default settings after an upgrade, in the Satellite web UI, navigate to Administer > Settings and click the Content tab.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-14 13:25:08 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 Justin Sherrill 2019-07-22 14:42:00 UTC

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

Comment 3 Justin Sherrill 2019-07-22 14:43:14 UTC

Connecting redmine issue https://projects.theforeman.org/issues/27367 from this bug

Comment 4 Justin Sherrill 2019-07-22 14:44:12 UTC

Proposing for 6.7 since the upstream issue will go into that and this needs docs  for release notes

Comment 5 Bryan Kearney 2019-07-30 20:08:05 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27367 has been resolved.

Comment 6 vijsingh 2019-11-16 11:32:12 UTC

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
___________________________________________________________________________________________________________________________________________________

Comment 10 errata-xmlrpc 2020-04-14 13:25:08 UTC

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