This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1254617 - [RFE] Provide a per custom repo metadata_expire configurable setting via UI and CLI
Summary: [RFE] Provide a per custom repo metadata_expire configurable setting via UI a...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 260381
TreeView+ depends on / blocked
 
Reported: 2015-08-18 13:56 UTC by Dave Sullivan
Modified: 2024-06-05 21:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-05 21:23:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1194714 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1220861 0 unspecified CLOSED Custom repositories do not define 'metadata_expire = 1' 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker   SAT-24092 0 None Migrated None 2024-06-05 21:23:50 UTC

Internal Links: 1194714 1220861

Description Dave Sullivan 2015-08-18 13:56:18 UTC 
Description of problem:

It's more convenient to handle this configuration in a single spot on the Sat6 Server side than to manage it from every client side per custom repo.
 
So the request here is to provide a configurable metadata_expire functionality administered from UI or CLI (hammer)


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

Sat 6.1.1



Additional info:

Mike McCunne mentioned it defaults to 1 and said that it currently not configurable.

While looking at this metadata_expire it might be worthwhile to look at any other options that yum provides as well.
Comment 1 Dave Sullivan 2015-08-18 14:01:40 UTC 
This BZ sounds similar to this request

https://bugzilla.redhat.com/show_bug.cgi?id=1194714
Comment 3 Mike McCune 2015-09-17 14:56:52 UTC 
Ensuring that we have a metadata expire at 1 ensures the systems always have the most current metadata and that updated content view publishes are *immediately* available to the end clients.

We are going to close this out as WONTFIX as the benefits of short expire times outweight custom, user editable expire times.

If there is a strong justification for this please feel free to re open.
Comment 4 Rafael Cardoso 2024-03-21 14:28:09 UTC 
Hello,


According to the request of the case #03754873, and also considering the last modification of this RFE on 09/2015, I wonder if such feature could be added to the next Satellite releases.


Thanks in advance.
Comment 5 Eric Helms 2024-06-05 21:23:51 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.