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):
Steps to Reproduce:
1. Mark a product "on_demand"
Both Satellite and Capsule(s) are "on_demand" or "immediate"
Individual setting for Satellite and Capsule
Connecting redmine issue http://projects.theforeman.org/issues/16808 from this bug
Upstream bug component is Capsule
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16808 has been resolved.
*** Bug 1484974 has been marked as a duplicate of this bug. ***
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?
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.