Bug 1434051
Summary: | [RFE] Disable Automatic content sync to Capsule on promotion | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | orabin |
Component: | Content Views | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2.7 | CC: | bbuckingham, bkearney, egolov, jcallaha, rjerrido, smeyer |
Target Milestone: | Unspecified | Keywords: | FutureFeature, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-07 07:16:55 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
orabin
2017-03-20 15:51:32 UTC
One of my customers is automatically publishing and promoting all their CCVs. New Capsule sync tasks are created while the others are still in progress and the customer ends up with dozens of Capsule sync tasks. While there should be an option to enable/disable syncs with a Capsule, the customer also like to see an option for "hammer content-view version promote" to start or prevent a sync of one, multiple or all Capsules. Examples: Disable all sync for all Capsules # hammer content-view version promote --content-view CV --no-capsule-sync Disable sync for some Capsules # hammer content-view version promote --content-view CV --no-capsule-sync=CAPSULE1,CAPSULE2 Sync to all Capsule # hammer content-view version promote --content-view CV --capsule-sync Sync to some Capsules # hammer content-view version promote --content-view CV --capsule-sync=CAPSULE1,CAPSULE2 This would give the customer more control when a sync over slower networks should be performed. *** This bug has been marked as a duplicate of bug 1305040 *** |