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.
Description of problem:
The Capsule synchronization is not initiated automatically after publishing/promoting new version of content view even when "Sync Capsules after content view promotion" is set to "Yes"
Version-Release number of selected component (if applicable): Satellite-6.13.0
How reproducible: Always
Steps to Reproduce:
1. Ensure setting "Sync Capsules after content view promotion" is set to "Yes"
2. Add Library lifecycle environment to Capsule. Enable and Sync any random repository on Satellite server.
3. Create a new lifecycle environment (say 'lc_new') and add 'lc_new' environment to the Capsule.
4. Create a new content view (say 'cv_new') and publish a new version of 'cv_new' to 'Library' lifecycle environment. Promote the newly published version of 'cv_new' to 'lc_new' lifecycle environment.
Actual results: Capsule synchronization is not automatically initiated even when a new repository is synchronized on Satellite. Also Capsule sync is not initiated automatically after publish/promote of 'cv_new' content view.
Expected results: Since Library environment is added to the Capsule, synchronizing new repository on Satellite should initiate Capsule sync. Also publish/promote of cv_new to lc_new environment should also initiate a Capsule sync task.