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	Flags:	jsherril: needinfo? (ayersmj)
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:

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.