Bug 1380799

Summary:	[RFE] individual on_demand for Satellite and Capsule
Product:	Red Hat Satellite	Reporter:	Beat Rubischon <brubisch>
Component:	Capsule	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED ERRATA	QA Contact:	Perry Gagne <pgagne>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.0	CC:	bbuckingham, brubisch, carlospec, cwelton, dgross, ealcaniz, fcami, jcallaha, jsherril, olivier.lardit, peter.vreman, rjerrido, sokeeffe
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
URL:	http://projects.theforeman.org/issues/16808
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:54:17 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:
Bug Depends On:
Bug Blocks:	1122832

Description Beat Rubischon 2016-09-30 14:58:47 UTC

Description of problem:

The current implementation of lazy_sync doesn't allow an online sync on the Satellite (to make sure all content is available in house when requested by a content host) and on demand sync on the capsules (where the network connectivity is in the hand of the customer).

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

6.2.2

How reproducible:

Always

Steps to Reproduce:
1. Mark a product "on_demand"
2.
3.

Actual results:

Both Satellite and Capsule(s) are "on_demand" or "immediate"

Expected results:

Individual setting for Satellite and Capsule

Additional info:

Comment 3 Justin Sherrill 2016-10-05 13:12:10 UTC

Connecting redmine issue http://projects.theforeman.org/issues/16808 from this bug

Comment 4 Bryan Kearney 2016-10-05 16:12:41 UTC

Upstream bug component is Capsule

Comment 5 Bryan Kearney 2016-10-31 20:19:10 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16808 has been resolved.

Comment 6 Justin Sherrill 2017-08-28 13:40:43 UTC

*** Bug 1484974 has been marked as a duplicate of this bug. ***

Comment 8 Justin Sherrill 2018-02-08 20:58:45 UTC

Hi, 

We are verifying this feature for Satellite 6.3 and had one clarification.  

The general intent of this bug was to provide per-capsule download policies, such that repositories could be synced using immediate on the satellite, but you a user could deploy a capsule using on_demand for all repositories.

Line 6 above seems to differ from that goal:  

A repository should be marked as on_demand (globally), immediate / on_demand (immediate on the Satellite, on_demand on the Capsules) or immediate (globally)


Is having a per-capsule download policy (that affects all repos on the capsule) sufficient for this customer?

Thanks

Comment 12 Satellite Program 2018-02-21 16:54:17 UTC

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> 
> For information on the advisory, and where to find the updated files, follow the link below.
> 
> If the solution does not work for you, open a new bug report.
> 
> https://access.redhat.com/errata/RHSA-2018:0336