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.
When promoting to a lifecycle environment, all of the capsules that are connected to the same environment get synced right away.
With multiple capsules on the same lifecycle environment, all starting to sync at the same time automatically this could cause significant load.
This also prevents syncing only during set maintenance windows.
Allowing to disable the automatic sync when promoting and allowing to initiate a sync later on would prevent having to cancel all running sync tasks when promoting outside the maintenance window.
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.