Bug 2257971

Summary: Optimized capsule sync doesn't sync recently published/promoted docker repositories
Product: Red Hat Satellite Reporter: afrid shaikh <shmohamm>
Component: Capsule - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.5CC: ahumbe, gpayelka, iballou, rlavi
Target Milestone: UnspecifiedKeywords: 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: 2024-02-16 18:37: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 afrid shaikh 2024-01-11 20:56:56 UTC 
Description of problem:
If user triggers an optimized Capsule sync manually after publishing/promoting a content view containing docker repositories. The capsule sync task doesn't sync anything.

Steps to Reproduce:
1. Set "Sync Capsules after content view promotion" to No
2. Create and sync a docker repository, using only one tag
3. Create a content view and attach the docker repository to it. Publish and promote the content view.
4. Trigger an optimized capsule sync to sync the CV repositories for the first time to the Capsule.
5. In the docker repository page, include a new tag and sync it.
6. Publish and promote a new version of the content view.
7. Trigger an optimized capsule sync again

Actual results:
The optimized capsule sync resyncs after the new publish, to capture the new tags.

Expected results:
Optimized capsule sync should sync the newly published docker repositories.

Additional info:
Requesting Fix release for satellite 6.12.z
Comment 2 Ian Ballou 2024-02-16 18:37:55 UTC 
Closing as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2227905

The fix is available in 6.12.5. Please reopen this issue if the issue is still presenting itself on 6.12.5 or later.

*** This bug has been marked as a duplicate of bug 2227905 ***