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 1660252 - [RFE] User control of Capsule sync policy and other traffic from Satellite to capsule
Summary: [RFE] User control of Capsule sync policy and other traffic from Satellite to...
Keywords:
Status: CLOSED DUPLICATE of bug 1305040
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.1.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Released
Assignee: Chris Roberts
QA Contact: Lukas Pramuk
URL: https://projects.theforeman.org/issue...
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2018-12-17 23:21 UTC by Mike McCune
Modified: 2019-10-07 16:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1305040
: 1684695 (view as bug list)
Environment:
Last Closed: 2019-03-01 22:08:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 25633 0 Normal Closed [RFE] User control of Capsule sync policy and other traffic from Satellite to capsule 2020-04-21 15:26:20 UTC
Github Katello katello pull 7871 0 None closed Fixes #25633 - Add setting for capsule autosync on cv promotion 2020-04-21 15:26:20 UTC

Description Mike McCune 2018-12-17 23:21:49 UTC
+++ This bug was initially created as a clone of Bug #1305040 +++

Proposed title of this feature request  
User can control the information send from Satellite to capsule.

Who is the customer behind the request?  
Account: name : Fidessa group plc
and acct #626489
  
TAM customer: no  
SRM customer: no  
Strategic: yes  
  
What is the nature and description of the request?  
Till now Satellite user cant control the information which is sent from Satellite to each capsule. Customer's Capsules are globally based in different time zones over limited bandwidth links.
In this scenario there should be an option to control over the information send from Satellite to capsule.

Does the customer have any specific time line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?  
  Customer cannot deploy any Capsules in Production until this is fixed.
  
Is the sales team involved in this request and do they have any additional input?  
No.

--- Additional comment from xdmoon on 20160211T00:11:13

in customer's words (attached Case # 01579041, Fidessa group plc, strategic):

"As far as I can see there is no fine grained control over when information is sent from Satellite to each capsule, it just gets put in the job queue and Satellite just does any data transfers when it decides. Whilst this is fine in a lab situation, in the real world when Capsules are globally based in different time zones often over limited bandwidth links, this method of transfer is not acceptable. When will there be fine grained control over the Satellite to multiple Capsule communications?"

--- Additional comment from pm-rhel on 20160218T16:31:43

This bug report previously had all acks and release flag approved.
However since at least one of its acks has been changed, the
release flag has been reset to ? by the bugbot (pm-rhel).  The
ack needs to become approved before the release flag can become
approved again.

--- Additional comment from xdmoon on 20160218T23:43:14

PM/Engineering/CEE Satellite RFE review status 2016/02/18:
This feature request has been accepted and aligned to some (yet uncommitted, likely post 6.3) future release of Satellite 6.
Xixi

--- Additional comment from myork on 20161122T11:43:58

I have another company (Fidelity UK), who would benefit from this. They have asked to raise an RFE, however it is an exact duplicate of this.

--- Additional comment from myork on 20161122T11:45:28

Any (rough, no-commital) idea when this may appear upstream ?

--- Additional comment from bkearney on 20180503T17:26:34

@rich, is there a dupe of this some place else?

--- Additional comment from rjerrido on 20180507T07:15:10

(In reply to Bryan Kearney from comment #6)
> @rich, is there a dupe of this some place else?

Yes, https://bugzilla.redhat.com/show_bug.cgi?id=1434051. I'll close 1434051 as a dupe of this BZ as this one has the higher PM score.

--- Additional comment from rjerrido on 20180507T07:16:55

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

--- Additional comment from bbuckingham on 20180718T17:07:34

Based on discussion with PM, the behavior requested by bug 1454578 would resolve this one as well.  Since this bug is older, we're closing bug 1454758; however, when solving this one, please consider the solution propoosed there.

e.g. -> Disable automatic capsule content sync when publishing new CV .

--- Additional comment from bbuckingham on 20180718T17:10:40

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

--- Additional comment from rjerrido on 20180821T17:06:29

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

--- Additional comment from bkearney on 20180821T19:44:42

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

--- Additional comment from rjerrido on 20180822T10:46:55

(adding a public comment #10 to make this BZ public)

Proposed title of this feature request  
User can control the information send from Satellite to capsule.


What is the nature and description of the request?  
Till now Satellite user cant control the information which is sent from Satellite to each capsule. Customer's Capsules are globally based in different time zones over limited bandwidth links.
In this scenario there should be an option to control over the information send from Satellite to capsule.

--- Additional comment from mmccune on 20180914T16:08:02

This RFE will also add support for controlling policy for if and when capsule syncs occur.

Currently Capsule syncs are always automatic after Content View publish and promotions and users may not want this automatic synchronization to occur and desire to instead control this manually.

Users may also wish to have a schedule in place, much like our existing Sync Plans but also apply to Capsule Syncs so they can know when the syncs occur.

--- Additional comment from bmidwood on 20181113T21:10:36

Maybe just a setting - don't sync to capsule

--- Additional comment from mmccune on 20181113T21:12:01

At the minimum level, ideally we could just offer a setting to disable the auto sync to capsules when a CV publishes or promotes.

Let the user control it via the API/CLI/UI when they want to sync.

--- Additional comment from mmccune on 20181217T16:46:12

I'm proposing this for 6.4.z (6.5.0) as it is almost complete upstream, is a small setting+change and is effecting a good# of customers at scale who are in the 'at risk' category or have been complaining about this issue for a long time.

Comment 2 Satellite Program 2018-12-18 01:11:22 UTC
Upstream bug assigned to chrobert

Comment 3 Satellite Program 2018-12-18 01:11:23 UTC
Upstream bug assigned to chrobert

Comment 5 Bryan Kearney 2019-01-15 20:02:19 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25633 has been resolved.

Comment 6 Bryan Kearney 2019-01-15 20:03:15 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25633 has been resolved.

Comment 7 Bryan Kearney 2019-01-15 20:04:25 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25633 has been resolved.

Comment 8 Bryan Kearney 2019-01-15 20:05:22 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25633 has been resolved.

Comment 9 Bryan Kearney 2019-01-15 20:06:18 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25633 has been resolved.

Comment 10 Bryan Kearney 2019-01-15 20:07:17 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25633 has been resolved.

Comment 11 Bryan Kearney 2019-01-15 20:08:30 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25633 has been resolved.

Comment 13 Mike McCune 2019-02-25 16:09:23 UTC
We need a docs bug filed in conjunction with this to help explain what this option does.

Comment 15 Mike McCune 2019-03-01 22:08:54 UTC
we don't need a clone against backlog as this is going in 6.4.z and 6.5.0

*** This bug has been marked as a duplicate of bug 1305040 ***

Comment 16 Mike McCune 2019-03-01 22:16:34 UTC
This bug was cloned and is still going to be included in the 6.4.3 release. It no longer has the sat-6.4.z+ flag and 6.4.3 Target Milestone Set which are now on the 6.4.z cloned bug. Please see the Clones field to track the progress of this bug in the 6.4.3 release.


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