Red Hat Bugzilla – Bug 1310199
[RFE] Enable Capsule to automatically sync after a publish/promotion
Last modified: 2016-12-19 10:08:08 EST
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
"hammer capsule content synchronize" must be run after every content view promotion leaving room for user error.
Capsule automatically synchronizes after promotion.
Moving 6.2 bugs out to sat-backlog.
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?
Based on comment 2, closing this bugzilla; however, please re-open with additional details the expected behavior is not being observed.