Bug 1220861

Summary:	Custom repositories do not define 'metadata_expire = 1'
Product:	Red Hat Satellite	Reporter:	Justin Sherrill <jsherril>
Component:	Content Management	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED CURRENTRELEASE	QA Contact:	sthirugn <sthirugn>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	bkearney, sthirugn, xdmoon
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/10495
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-12 14:01:12 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 2015-05-12 15:57:29 UTC

Description of problem:

Currently candlepin sets redhat repos to use 'metadata_expire = 1' in the redhat.repo file. 

Custom repositories do not have this set, and it is up to katello to set it.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create a custom repo
2. Register a client
3. attach client to custom repo
4.  Example /etc/yum.repos.d/redhat.repo

Actual results:
metadata_expire is not set for the custom repo

Expected results:
metadata_expire is set to 1 for the custom repo

Additional info:

Comment 1 Justin Sherrill 2015-05-12 15:58:01 UTC

Note:  This was discovered by a user using the sat6.1 beta

Comment 4 Justin Sherrill 2015-05-13 12:02:04 UTC

Created redmine issue http://projects.theforeman.org/issues/10495 from this bug

Comment 5 Bryan Kearney 2015-05-15 17:55:25 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/10495 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|78c75ae85c8a5752de9e655f1ec278f492f95245.

Comment 8 sthirugn@redhat.com 2015-05-21 19:07:39 UTC

Verified in Sat 6.1 GA Snap 5.  I had two repositories in my content view - one is RH repo and other is custom repo.  Both are set to expire_metadata=1.

Comment 10 Bryan Kearney 2015-08-11 13:35:57 UTC

This bug is slated to be released with Satellite 6.1.

Comment 11 Bryan Kearney 2015-08-12 14:01:12 UTC

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.