Bug 1388927 - [RFE] As a user, I want to trigger a "background sync" for repositories in content view versions.
Summary: [RFE] As a user, I want to trigger a "background sync" for repositories in co...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.2.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-26 13:32 UTC by Tom McKay
Modified: 2020-12-14 07:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-10-12 19:30:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14385 0 Normal New As a user, I want to trigger a "background sync" for repositories in content view versions. 2020-09-18 18:02:00 UTC
Red Hat Knowledge Base (Solution) 2739671 0 None None None 2016-10-31 08:31:27 UTC

Description Tom McKay 2016-10-26 13:32:23 UTC
The use case:
1. Sync "RHEL 7Server" repo in on-demand download policy
2. Create a CV w/ filters to reduce packages from 14000 to 4
3. Publish CV to get CVV 1.0
4. Attempting to export CVV 1.0 will error since the packages have not yet been downloaded

I would like to be able to force pulp to download the 4 packages in that repo. This is equivalent to a "background" download policy in results.

I am not defining how this is implemented but would like to see it either at the repository level or at the content view version level. Something like this

<pre>
hammer content-view version synchronize --id 12
</pre>

Comment 1 Tom McKay 2016-10-26 13:32:27 UTC
Created from redmine issue http://projects.theforeman.org/issues/14385

Comment 3 Peter Vreman 2016-10-26 14:28:52 UTC
As a user is have another use case that is similiar.
During deployment i do not want any dependency on the RedHat CDN. Once i publish a ContentView then i want that all RPMs are available after the publishing finishes.

This makes sure that my Satellite always have all RPMs available for all published ContentViews.
But from the CDN downloads on all used packages and therefor improves the initial sync time to not download GBs of unused packcages, e.g. old kernel versions that will never be published to any host.

Comment 4 Peter Vreman 2016-10-26 14:30:51 UTC
For this use case a proposed download_policy name is 'published'

Comment 9 Bryan Kearney 2017-10-12 19:30:13 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


Note You need to log in before you can comment on or make changes to this bug.