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.
Let's investigate https://bugzilla.redhat.com/show_bug.cgi?id=2173535 at the same time as looking into this issue.