Bug 1310199 - [RFE] Enable Capsule to automatically sync after a publish/promotion [NEEDINFO]
Summary: [RFE] Enable Capsule to automatically sync after a publish/promotion
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.1.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 17:48 UTC by Michael J. Ayers
Modified: 2019-09-26 13:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-19 15:08:08 UTC
Target Upstream Version:
jsherril: needinfo? (ayersmj)

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.