Project

General

Profile

Bug #10495

Custom repositories do not define 'metadata_expire = 1'

Added by Justin Sherrill about 7 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Web UI
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1220861
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:

Associated revisions

Revision 78c75ae8 (diff)
Added by Justin Sherrill about 7 years ago

fixes #10495 - create custom products with metadata_expire set to 1

also provide upgrade rake task
Red Hat products will have it set to 1 via candlepin

Revision 0258943e
Added by Justin Sherrill about 7 years ago

Merge pull request #5226 from jlsherrill/10495

fixes #10495 - create custom products with metadata_expire set to 1

History

#1 Updated by The Foreman Bot about 7 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/5226 added
  • Pull request deleted ()

#2 Updated by Justin Sherrill about 7 years ago

  • Legacy Backlogs Release (now unused) set to 51

#3 Updated by Justin Sherrill about 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Eric Helms about 7 years ago

  • Triaged changed from No to Yes

Also available in: Atom PDF