Actions
Bug #10495
closed
Custom repositories do not define 'metadata_expire = 1'
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
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:
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/5226 added
- Pull request deleted (
)
Updated by Justin Sherrill over 9 years ago
- Translation missing: en.field_release set to 51
Updated by Justin Sherrill over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|78c75ae85c8a5752de9e655f1ec278f492f95245.
Updated by
Actions