Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1310199

Summary:	[RFE] Enable Capsule to automatically sync after a publish/promotion
Product:	Red Hat Satellite	Reporter:	Michael J. Ayers <ayersmj>
Component:	Capsule - Content	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.1.6	CC:	ayersmj, bbuckingham, jsherril
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-19 15:08:08 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:
Embargoed:

Description Michael J. Ayers 2016-02-19 17:48:19 UTC

Description of problem:
Give Satellite ability to have capsule syncs happen automatically after a promotion of a content view or other modification.  Currently it appears that "hammer capsule content synchronize" must be run after every content view promotion leaving room for user error.

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


Actual results:
"hammer capsule content synchronize" must be run after every content view promotion leaving room for user error.

Expected results:
Capsule automatically synchronizes after promotion.

Additional info:

Comment 1 Bryan Kearney 2016-07-26 19:04:17 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 2 Justin Sherrill 2016-09-13 19:23:35 UTC

This actually happens already all the way back to Satellite 6.0.  

Whenever you publish/promote a content view into a lifecycle environment associated to the capsule, any capsule associated to that lifecycle environment will be synced.

Do you have reason to believe this isn't working?

Comment 3 Brad Buckingham 2016-12-19 15:08:08 UTC

Based on comment 2, closing this bugzilla; however, please re-open with additional details the expected behavior is not being observed.

Comment 4 Red Hat Bugzilla 2023-09-14 03:18:15 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days